From: Christoph Hellwig <hch@caldera.de>
To: Ben LaHaise <bcrl@redhat.com>
Cc: linux-mm@kvack.org
Subject: Re: 2.5 page cache improvement idea
Date: Tue, 27 Feb 2001 01:41:51 +0100 [thread overview]
Message-ID: <20010227014150.A5426@caldera.de> (raw)
In-Reply-To: <Pine.LNX.4.30.0102261829330.5576-100000@today.toronto.redhat.com>; from bcrl@redhat.com on Mon, Feb 26, 2001 at 06:46:24PM -0500
On Mon, Feb 26, 2001 at 06:46:24PM -0500, Ben LaHaise wrote:
> Hey folks,
>
> Here's an idea I just bounced off of Rik that seems like it would be
> pretty useful. Currently the page cache hash is system wide. For 2.5,
> I'm suggesting that we make the page cache hash a per-inode structure and
> possibly move the page index and mapping into the structure's information.
> Also, for dealing with hash collisions (which are going to happen under
> certain well known circumstances), we could move to a b*tree structure
> hanging off of the hashes. So we'd have a data structure that looks like
> the following:
>
>
> inode
Shouldn't this be address_space instead?
>
> -> hash table
> -> struct page, index, mapping
> -> head of b*tree for overflow
>
> page
> -> pointer back to hash bucket/b*tree entry
>
> These changes would replace ~20 bytes in struct page with one pointer.
Looks sane - the elimination of a systemwide resource should improve
scalability a lot - if it comes together with size reduction of major
structure only the side effects need some thoughs :P
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-02-27 0:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 23:46 Ben LaHaise
2001-02-27 0:41 ` Christoph Hellwig [this message]
2001-02-27 2:42 ` Chuck Lever
2001-02-27 2:49 ` Ben LaHaise
2001-02-27 3:26 ` Gerrit Huizenga
2001-02-27 5:47 ` Kanoj Sarcar
2001-02-27 9:05 ` Gerrit Huizenga
2001-02-27 9:21 ` Kanoj Sarcar
2001-02-27 13:42 ` Andrea Arcangeli
2001-02-27 11:52 ` Stephen C. Tweedie
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=20010227014150.A5426@caldera.de \
--to=hch@caldera.de \
--cc=bcrl@redhat.com \
--cc=linux-mm@kvack.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