linux-kernel - Re: userspace pagecache management tool

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070304040742.e56fc57f.akpm@linux-foundation.org>
Date:	Sun, 4 Mar 2007 04:07:42 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Rik van Riel <riel@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: userspace pagecache management tool

On Sat, 03 Mar 2007 20:56:27 -0500 Rik van Riel <riel@...hat.com> wrote:

> Andrew Morton wrote:
> 
> >>> Doing a refault thing would help a bit, but stops working at a certain point.
> >> At what point does it stop working?
> > 
> > We need to store that this-page-got-reclaimed info somewhere.  I don't know
> > how space-efficient that is.  Did anyone ever do an implementation?
> 
> One 32 bit word per evicted page that we keep track of.

ok...

I wonder if we really need a new data structure to track that.  I mean,
once a file-backed (or indeed swapcache) page has been reclaimed, its
radix-tree slot is just sitting there with zeroes in it, asking us to reuse
that space for something interesting, no?

Of course, if all 64 pages in a radix-tree node get removed, we'll
currently free the node itself.  We could stop doing that, but the effects
of that might be pretty bad sometimes.  Instead, it sounds sensible to
populate the now-null slot in the parent radix-tree node with an
average/max/min/per-child-bitmap/whatever of the metrics for the 64
non-resident pages which that non-leaf slot represents.  So as the period
since a single page got evicted increases and increases, our information
about its state becomes less and less accurate.

If that inaccuracy is a problem then perhaps we could defer the collapsing
of a now-empty node into its parent in some manner.

> > You mean design it and review the design before coding it?  You'll find few
> > objections there.
> 
> Few objections, but sadly also very few people interested in
> actually reviewing the design :(
> 
> If you can find holes in http://linux-mm.org/PageReplacementDesign
> please let me know :)

That all looks pretty non-crazy and implementable to me.  Alas, getting the
stuff written and working is 1% of the effort.  The rest is the nasty hunt
for new corner-cases and general productisation hassle.  But if initial
results show benefit, I expect we could manage all that.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/