All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Scalable page cache - take two
Date: Sun, 23 Dec 2001 16:28:39 -0800	[thread overview]
Message-ID: <20011223162839.B750@holomorphy.com> (raw)
In-Reply-To: <87bsgp7fcq.fsf@fadata.bg>
In-Reply-To: <87bsgp7fcq.fsf@fadata.bg>; from velco@fadata.bg on Mon, Dec 24, 2001 at 12:15:33AM +0200

On Mon, Dec 24, 2001 at 12:15:33AM +0200, Momchil Velikov wrote:
> This is the second mutation of the scalable page cache patch.  It:
> 
>         - removes the global page cache hash table and the associated lock
> 
> 	- implements the page cache as a per mapping radix tree. This
>           increases the size of ``struct inode'' by 8 bytes (in 32bit
>           ports).  The branch factor is a compile time constant
>           ``RAD_MAP_SHIFT'' (currently 7, 128 pointers)
> 
>         - decreases the size of ``struct page'' by removing
>           ``next_hash'' and ``pprev_hash' fields as they are no longer
>           needed for the page cache.  NOTE that this curently breaks
>           sparc64 and arm ports. The sparc64 port is trivialy fixable.
> 
> The patch is stable on UP (survives make -j6) and does not have
> noticeable performance impact (at least for the kernel compile
> benchmark) in either direction.

Beautiful programming!


Cheers,
Bill

  reply	other threads:[~2001-12-24  0:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-23 22:15 [PATCH] Scalable page cache - take two Momchil Velikov
2001-12-24  0:28 ` William Lee Irwin III [this message]
2001-12-24  0:52 ` Anton Blanchard
2001-12-27  6:15   ` Daniel Phillips
2001-12-24 17:08 ` Heinz Diehl

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=20011223162839.B750@holomorphy.com \
    --to=wli@holomorphy.com \
    --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.