LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Andrew Morton <akpm@osdl.org>,
Benoit Boissinot <bboissin@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: 2.6.19-rc5-mm1 progression
Date: Wed, 06 Dec 2006 08:32:21 -0600 [thread overview]
Message-ID: <4576D475.6090802@lwfinger.net> (raw)
In-Reply-To: <1165407170.12561.12.camel@twins>
Peter Zijlstra wrote:
> On Mon, 2006-12-04 at 21:32 -0600, Larry Finger wrote:
>> Andrew Morton wrote:
>>> On Fri, 24 Nov 2006 17:36:27 +0100
>>> "Benoit Boissinot" <bboissin@gmail.com> wrote:
>>>
>>>> On 11/24/06, Larry Finger <Larry.Finger@lwfinger.net> wrote:
>>>>> Is there the equivalent of 'git bisect' for the -mmX kernels?
>>>>>
>>>> http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt
>>>>
>>> Please take the time to do that. Yours is an interesting report - I'm not
>>> aware of anything in there which was expected to cause a change of this
>>> mature.
>>>
>> There are at least two patches in 2.6.19-rc5-mm2 that make my system much more responsive for
>> interactive jobs. The one that has the majority of the effect is:
>>
>> radix-tree-rcu-lockless-readside.patch
>>
>> I have not been able to isolate the second patch, which has the lesser effect. All I can say is that
>> it occurred before the above patch in patches/series. This patch was tested against 2.6.19 and fixed
>> most of the problem on that version.
>
> Curious...
>
> This patch introduces the direct pointer optimisation for single element
> radix trees and makes the radix tree safe to read in a lock-less manner
> which is not used -yet-. The only difference that that should have is
> that the elements are freed using rcu callback instead of directly.
>
> /me puzzled how this has a large effect on interactivity.
I also wondered why this patch should have the effect as it didn't seem in an area that should be
important. I did test it on both 2.6.19-rc5-mm2 and vanilla 2.6.19. In both cases, it made
interactive response improve.
One single task that seems to have the biggest effect on my unpatched systems is the link step for a
new kernel. I am assuming that this process calls for lots of virtual memory. One other
characteristic of my system when it gets unresponsive is that kswapd is running regularly; however,
I have never observed any swap file usage.
Larry
next prev parent reply other threads:[~2006-12-06 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 16:08 Larry Finger
2006-11-24 16:36 ` Benoit Boissinot
2006-11-25 19:24 ` Andrew Morton
2006-11-25 21:28 ` Larry Finger
2006-12-05 3:32 ` Larry Finger
2006-12-06 12:12 ` Peter Zijlstra
2006-12-06 14:32 ` Larry Finger [this message]
2006-12-07 9:36 ` Nick Piggin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4576D475.6090802@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=bboissin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--subject='Re: 2.6.19-rc5-mm1 progression' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).