public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: harald.holzer@eunet.at, linux-kernel@vger.kernel.org,
	wookie@osdl.org, velco@fadata.bg
Subject: Re: i686 SMP systems with more then 12 GB ram with 2.4.x kernel ?
Date: Thu, 3 Jan 2002 15:33:55 +0100	[thread overview]
Message-ID: <20020103153355.612bd269.skraw@ithnet.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0201031106590.24031-100000@imladris.surriel.com>
In-Reply-To: <1010015450.15492.19.camel@hh2.hhhome.at> <Pine.LNX.4.33L.0201031106590.24031-100000@imladris.surriel.com>

On Thu, 3 Jan 2002 11:28:45 -0200 (BRST)
Rik van Riel <riel@conectiva.com.br> wrote:

> Another item to look into is removing the page cache hash table
> and replacing it by a radix tree or hash trie, in the hopes of
> improving scalability while at the same time saving some space.

Ah, didn't we see such a patch lately in LKML? If I remember correct I saw some
comparison charts too and some people testing it were happy with it. Just
searched through the list: 24. dec :-) by Momchil Velikov Can someone with big
mem have a look at the saving? How about 18-pre?

Regards,
Stephan

  reply	other threads:[~2002-01-03 14:35 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-29 18:18 i686 SMP systems with more then 12 GB ram with 2.4.x kernel ? Harald Holzer
2001-12-29 18:45 ` Alan Cox
2001-12-29 21:24   ` M. Edward (Ed) Borasky
2001-12-30  0:25     ` M. Edward (Ed) Borasky
2001-12-30  2:14       ` Harald Holzer
2001-12-30  2:33         ` M. Edward Borasky
2002-01-01 18:15   ` M. Edward Borasky
2002-01-01 18:46     ` Alan Cox
2002-01-01 19:02       ` M. Edward Borasky
2002-01-02  1:16       ` H. Peter Anvin
2002-01-02 21:17       ` Gerrit Huizenga
2002-01-06  8:20         ` Benjamin LaHaise
2002-01-06 16:16           ` Alan Cox
2002-01-06 20:23             ` Benjamin LaHaise
2002-01-06 23:37             ` Chris Wedgwood
2002-01-07  0:29               ` The COUGAR Project M. Edward Borasky
2002-01-07  2:18               ` i686 SMP systems with more then 12 GB ram with 2.4.x kernel ? Marvin Justice
2002-01-07  2:38                 ` Chris Wedgwood
2002-01-07  4:40                   ` T. A.
2002-01-07 16:20             ` Hugh Dickins
2002-01-02 17:30 ` Timothy D. Witham
     [not found]   ` <1009994687.12942.14.camel@hh2.hhhome.at>
     [not found]     ` <1009995669.1253.17.camel@wookie-laptop.pdx.osdl.net>
2002-01-02 23:50       ` Harald Holzer
2002-01-03  0:16         ` Alan Cox
2002-01-03 13:30           ` Rik van Riel
2002-01-04 12:09             ` Hugh Dickins
2002-01-04 12:15               ` Rik van Riel
2002-01-03  0:17         ` Mark Zealey
2002-01-03 13:28         ` Rik van Riel
2002-01-03 14:33           ` Stephan von Krawczynski [this message]
2002-01-03 16:38             ` Rik van Riel
2002-01-03 15:15         ` Anton Blanchard
  -- strict thread matches above, loose matches on Subject: below --
2001-12-29 19:25 Dieter Nützel
2002-01-06 18:39 Daniel Freedman
2002-01-06 18:59 ` Marvin Justice
2002-01-06 19:45   ` Daniel Freedman
2002-01-06 20:15     ` Marvin Justice
2002-01-07  5:17       ` Daniel Freedman

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=20020103153355.612bd269.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=harald.holzer@eunet.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=velco@fadata.bg \
    --cc=wookie@osdl.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