From: Daniel Phillips <phillips@bonn-fries.net>
To: William Lee Irwin III <wli@holomorphy.com>,
Peter W?chtler <pwaechtler@loewe-komp.de>
Cc: Christoph Hellwig <hch@caldera.de>,
linux-mm@kvack.org, lkml <linux-kernel@vger.kernel.org>,
velco@fadata.bg
Subject: Re: [PATCH] updated version of radix-tree pagecache
Date: Mon, 7 Jan 2002 13:53:12 +0100 [thread overview]
Message-ID: <E16NZHB-0001Q7-00@starship.berlin> (raw)
In-Reply-To: <20020107030344.H10391@holomorphy.com>
On January 7, 2002 12:03 pm, William Lee Irwin III wrote:
> On Mon, Jan 07, 2002 at 11:05:08AM +0100, Peter W?chtler wrote:
> > Can you sum up the advantages of this implementation?
> > I think it scales better on "big systems" where otherwise you end up
> > with many pages on the same hash?
> >
> > Is it beneficial for small systems? (I think not)
>
> I speculate this would be good for small systems as well as it reduces
> the size of struct page by 2*sizeof(unsigned long) bytes, allowing more
> incremental allocation of pagecache metadata. I haven't tried it on my
> smaller systems yet (due to lack of disk space and needing to build the
> cross-toolchains), though I'm now curious as to its exact behavior there.
Benchmark it on UML. In my experience, performance on UML is quite predictive of
performance on native systems.
--
Daniel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-01-07 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 16:12 Christoph Hellwig
2002-01-07 10:05 ` Peter Wächtler
2002-01-07 10:07 ` Momchil Velikov
2002-01-07 11:03 ` William Lee Irwin III
2002-01-07 12:52 ` Daniel Phillips
2002-01-07 12:53 ` Daniel Phillips [this message]
2002-01-11 23:21 ` Pavel Machek
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=E16NZHB-0001Q7-00@starship.berlin \
--to=phillips@bonn-fries.net \
--cc=hch@caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pwaechtler@loewe-komp.de \
--cc=velco@fadata.bg \
--cc=wli@holomorphy.com \
/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