From: Daniel Phillips <phillips@arcor.de>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Race in shrink_cache
Date: Thu, 5 Sep 2002 22:00:14 +0200 [thread overview]
Message-ID: <E17n2nX-0006Ah-00@starship> (raw)
In-Reply-To: <3D77AEED.5ADAA4@zip.com.au>
On Thursday 05 September 2002 21:22, Andrew Morton wrote:
> Daniel Phillips wrote:
> >
> > On Thursday 05 September 2002 20:51, Andrew Morton wrote:
> > > Daniel Phillips wrote:
> > > >
> > > > ..
> > > > On the other hand, if what you want is a private list that page_cache_release
> > > > doesn't act on automatically, all you have to do is set the lru state to zero,
> > > > leave the page count incremented and move to the private list. You then take
> > > > explicit responsibility for freeing the page or moving it back onto a
> > > > mainstream lru list.
> > >
> > > That's the one. Page reclaim speculatively removes a chunk (typically 32) of
> > > pages from the LRU, works on them, and puts back any unfreeable ones later
> > > on.
> >
> > Convergent evolution. That's exactly the same number I'm handling as a
> > chunk in my rmap sharing project (backgrounded for the moment). In this
> > case, the 32 comes from the number of bits you can store in a long, and
> > it conveniently happens to fall in the sweet spot of performance as well.
>
> That's SWAP_CLUSTER_MAX. I've never really seen a reason to change
> its value. On 4k pagesize.
>
> The pagevecs use 16 pages. The thinking here is that we want it to
> be large enough to be efficient, but small enough so that all the
> pageframes are still in L1 when we come around and hit on them again.
> Plus pagevecs are placed on the stack.
>
> > ...
> > I think the extra refcount strategy is inherently stronger, and this
> > is an example of why. The other would require you to take/drop an
> > extra count explicitly for your private list.
>
> OK. I assume you taught invalidate_inode_pages[2] about the extra ref?
Yes, all the magic tests have been replaced with versions that depend on
the LRU_PLUS_CACHE define (1 or 2). As a side effect, this lets you find
all the places that care about this with a simple grep, so I'd be inclined
to leave the symbol in, even after we decide which setting we prefer.
--
Daniel
next prev parent reply other threads:[~2002-09-05 19:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 5:04 Daniel Phillips
2002-09-05 6:36 ` Andrew Morton
2002-09-05 6:36 ` Daniel Phillips
2002-09-05 7:07 ` Andrew Morton
2002-09-05 7:28 ` Daniel Phillips
2002-09-05 7:53 ` Andrew Morton
2002-09-05 18:41 ` Daniel Phillips
2002-09-05 18:51 ` Andrew Morton
2002-09-05 19:08 ` Daniel Phillips
2002-09-05 19:22 ` Andrew Morton
2002-09-05 20:00 ` Daniel Phillips [this message]
2002-09-05 13:33 ` Rik van Riel
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=E17n2nX-0006Ah-00@starship \
--to=phillips@arcor.de \
--cc=akpm@zip.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®