From: Christoph Hellwig <hch@ns.caldera.de>
To: mingo@elte.hu (Ingo Molnar)
Cc: "David S. Miller" <davem@redhat.com>,
Momchil Velikov <velco@fadata.bg>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Scalable page cache
Date: Mon, 26 Nov 2001 19:08:20 +0100 [thread overview]
Message-ID: <200111261808.fAQI8KK26768@ns.caldera.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0111262026120.15876-100000@localhost.localdomain>
Hi Ingo,
In article <Pine.LNX.4.33.0111262026120.15876-100000@localhost.localdomain> you wrote:
> On 26 Nov 2001, Momchil Velikov wrote:
>
>> Yep. Folks on #kernelnewbies told me about it, when there were only
>> changes to ``shrink_cache'' left. So, I decided to funish mine ;)
>
> ok :) A search on Google for 'scalable pagecache' brings you straight to
> our patch. I've uploaded the patch against 2.4.16 as well:
>
> http://redhat.com/~mingo/smp-pagecache-patches/pagecache-2.4.16-A1
>
> this is a (tested) port of the patch to the latest VM.
This patch seems to have a number of interesting changes compared to
older versions.
- do_generic_file_read() now takes an additional integer parameter,
'nonblock'. This one always is zero, though. Why do you break
the interface?
- there is a new global function, flush_inode_pages(). It is not
used at all. What is this one supposed to do?
- file_send_actor() is no more static in mm/filemap.c. I'm perfectly
fine with that as I will need that for the UnixWare sendv64 emulation
in Linux-ABI, but again no user outside of filemap.c exists.
- you change a number of parameters called 'offset' into 'index',
this makes sense to me, but doesn't really belong into this diff..
- due to the additional per-bucket spinlock the pagecache size
dramatically increases. Wouldn't it be a good idea to switch to
bootmem allocation so very big machines still can have the full
size, not limited by __get_free_pages failing?
next prev parent reply other threads:[~2001-11-26 18:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 12:31 Momchil Velikov
2001-11-26 17:22 ` Ingo Molnar
2001-11-26 17:23 ` Momchil Velikov
2001-11-26 18:16 ` Benjamin LaHaise
2001-11-26 18:33 ` David S. Miller
2001-11-26 19:29 ` Andrew Morton
2001-11-26 19:35 ` David S. Miller
2001-11-26 18:42 ` Rik van Riel
2001-11-26 20:29 ` Ingo Molnar
2001-11-26 18:34 ` Benjamin LaHaise
2001-11-26 20:40 ` Ingo Molnar
2001-11-26 19:19 ` Benjamin LaHaise
2001-11-26 21:00 ` Ingo Molnar
2001-11-26 20:43 ` Daniel Phillips
2001-11-26 19:18 ` David S. Miller
2001-11-26 19:45 ` Andrew Morton
2001-11-26 19:57 ` David S. Miller
2001-11-26 20:03 ` Andrew Morton
2001-11-26 20:37 ` Linus Torvalds
2001-11-26 21:02 ` Andrew Morton
2001-11-26 22:23 ` Linus Torvalds
2001-11-26 22:49 ` Jeff Garzik
2001-11-26 23:06 ` Linus Torvalds
2001-11-26 19:49 ` Ingo Molnar
2001-11-26 18:08 ` Christoph Hellwig [this message]
2001-11-26 20:13 ` Ingo Molnar
2001-11-26 21:09 ` Ingo Molnar
2001-11-26 21:10 ` Ingo Molnar
2001-11-26 17:29 ` Linus Torvalds
2001-11-26 20:03 ` Ingo Molnar
2001-11-26 18:52 ` Daniel Phillips
2001-11-26 18:02 ` David S. Miller
2001-11-26 18:11 ` Rik van Riel
2001-11-27 8:07 ` benchmark results: " Anton Blanchard
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=200111261808.fAQI8KK26768@ns.caldera.de \
--to=hch@ns.caldera.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=velco@fadata.bg \
/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
all inboxes | Powered by JetHome®