From: David Chinner <dgc@sgi.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Per-superblock unused dentry LRU lists.
Date: Wed, 24 May 2006 15:47:23 +1000 [thread overview]
Message-ID: <20060524054723.GF7418631@melbourne.sgi.com> (raw)
In-Reply-To: <1148444589.3049.26.camel@laptopd505.fenrus.org>
On Wed, May 24, 2006 at 06:23:09AM +0200, Arjan van de Ven wrote:
> On Wed, 2006-05-24 at 14:01 +1000, David Chinner wrote:
> > Yup, that is what the current code I've written will do. I just
> > wanted someting that worked over all superblocks to begin with.
> > It's not very smart, but improving it can be done incrementally.
>
> I think that if you say A you should say B, I mean, if you make the list
> per SB you probably just should do the step and make at least the
> counter per SB as well. That will also save in cacheline bounces I
> suppose... but more importantly you keep the counters next to the list.
But it doesn't remove the need for the global counter. The
dcache_lock is far more heavily contended so the counter cacheline
bouncing is lost in the noise here. No to mention the counter can
only be updated while holding the dcache_lock. Hence at this point,
adding per-sb counters is pure overhead unless the reclaim method
is made to use them.
> Which you'll also need to do any kind of scaling I suppose later on, so
> might as well keep the stats already.
The per-sb list improves scalability only by reducing the maximum
length of time the dcache_lock is held. Scalabilty for further
parallelism (and therefore better reclaim performance) is going to
require locking changes so that's when I'd expect the counters to
need changing. I don't want to over-optimise before we know what we
actually need to optimise...
Cheers,
Dave.
--
Dave Chinner
R&D Software Enginner
SGI Australian Software Group
next prev parent reply other threads:[~2006-05-24 5:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 1:24 [PATCH] Per-superblock unused dentry LRU lists David Chinner
2006-05-24 1:24 ` David Chinner
2006-05-24 1:44 ` Randy.Dunlap
2006-05-24 1:44 ` Randy.Dunlap
2006-05-24 1:48 ` David Chinner
2006-05-24 1:48 ` David Chinner
2006-05-24 1:59 ` Arjan van de Ven
2006-05-24 4:01 ` David Chinner
2006-05-24 4:23 ` Arjan van de Ven
2006-05-24 5:47 ` David Chinner [this message]
2006-05-24 5:02 ` Balbir Singh
2006-05-24 5:02 ` Balbir Singh
2006-05-24 6:19 ` David Chinner
2006-05-24 6:19 ` David Chinner
2006-05-24 7:06 ` Balbir Singh
2006-05-24 8:15 ` David Chinner
2006-05-24 8:28 ` Balbir Singh
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=20060524054723.GF7418631@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=arjan@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--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.