From: Maneesh Soni <maneesh@in.ibm.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: LKML <linux-kernel@vger.kernel.org>,
lse-tech <lse-tech@lists.sourceforge.net>
Subject: Re: [RFC] dcache scalability patch (2.4.17)
Date: Mon, 15 Jul 2002 13:19:33 +0530 [thread overview]
Message-ID: <20020715131933.C13618@in.ibm.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0207121021430.11261-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Fri, Jul 12, 2002 at 10:29:53AM -0400
On Fri, Jul 12, 2002 at 10:29:53AM -0400, Alexander Viro wrote:
>
>
> On Fri, 12 Jul 2002, Maneesh Soni wrote:
>
> > Here is the dcache scalability patch (cleaned up) as disscussed in
> > the previous post to lkml by Dipankar. The patch uses RCU for doing fast
> > dcache lookup. It also does lazy updates to lru list of dentries to
> > avoid doing write operations while doing lookup.
>
> Where is
> * version for 2.5.<current>
> * analysis of benefits in real-world situations for 2.5 version?
>
> Patch adds complexity and unless you can show that it gives significant
> benefits outside of pathological situations, it's not going in.
>
> Note: measurements on 2.4 do not make sense; reduction of cacheline
> bouncing between 2.4 and 2.5 will change the results anyway and
> if any of these patches are going to be applied to 2.4, reduction of
> cacheline bouncing on ->d_count is going to go in before that one.
Hi Viro,
The 2.4 tests we did, also has fastwalk patch ported from 2.5. Though
fastwalk has performed better (throughput improved by 1%) than base 2.4
but I think because of increased hold and wait times on dcache_lock, results
are not as good as using only dcache_rcu.
http://marc.theaimsgroup.com/?l=linux-kernel&m=102645767914212&w=2
For 2.5 I tried to merge fastwalk and dcache_rcu but both doesnot seem
to compliment each other. fastwalk takes dcache_lock much earlier than
d_lookup.
On 2.5 we get better results from dcache_rcu when we reomve
fastwalk and put the dcache code back to 2.5.10ish level of code. Probably
this is not the correct way as it involves lots of code changes and we need
to workout some other way.
There are some numbers from 2.5.20-base vs dcache_rcu(no fastwalk) done by
Anton Blanchard with dbench.
http://samba.org/~anton/linux/2.5.20/
Regards,
Maneesh
--
Maneesh Soni
IBM Linux Technology Center,
IBM India Software Lab, Bangalore.
Phone: +91-80-5044999 email: maneesh@in.ibm.com
http://lse.sourceforge.net/locking/rcupdate.html
prev parent reply other threads:[~2002-07-15 7:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 14:09 [RFC] dcache scalability patch (2.4.17) Maneesh Soni
2002-07-12 14:13 ` [Lse-tech] " Christoph Hellwig
2002-07-12 16:20 ` Dipankar Sarma
2002-07-15 8:10 ` Maneesh Soni
2002-07-15 8:25 ` Maneesh Soni
2002-07-12 14:29 ` Alexander Viro
2002-07-12 16:10 ` [Lse-tech] " Dipankar Sarma
2002-07-12 18:02 ` Dipankar Sarma
2002-07-12 18:10 ` Hanna Linder
2002-07-12 17:35 ` Paul Menage
2002-07-13 8:52 ` Alexander Viro
2002-07-13 17:25 ` Paul Menage
2002-07-13 17:33 ` Alexander Viro
2002-07-13 17:51 ` Paul Menage
2002-07-13 17:54 ` Alexander Viro
2002-07-15 0:10 ` Linus Torvalds
2002-07-12 22:50 ` Hanna Linder
2002-07-15 7:49 ` Maneesh Soni [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=20020715131933.C13618@in.ibm.com \
--to=maneesh@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=viro@math.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox