From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Andrew Morton <akpm@osdl.org>,
Benoit Boissinot <bboissin@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc5-mm1 progression
Date: Thu, 07 Dec 2006 20:36:21 +1100 [thread overview]
Message-ID: <4577E095.1040904@yahoo.com.au> (raw)
In-Reply-To: <1165407170.12561.12.camel@twins>
Peter Zijlstra wrote:
> On Mon, 2006-12-04 at 21:32 -0600, Larry Finger wrote:
>>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.
>
> Nick?
I have already got the direct data optimisation upstream. It might be
possible that it is some interaction with the extra rcu callbacks going
off... I don't know :\
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
prev parent reply other threads:[~2006-12-07 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 16:08 2.6.19-rc5-mm1 progression 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
2006-12-07 9:36 ` Nick Piggin [this message]
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=4577E095.1040904@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Larry.Finger@lwfinger.net \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=bboissin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.