From: ebiederm@xmission.com (Eric W. Biederman)
To: Chris Mason <mason@suse.com>
Cc: Daniel Phillips <phillips@bonn-fries.net>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
torvalds@transmeta.com
Subject: Re: [RFC] using writepage to start io
Date: 06 Aug 2001 09:13:20 -0600 [thread overview]
Message-ID: <m11ympw7an.fsf@frodo.biederman.org> (raw)
In-Reply-To: <209120000.997036451@tiny>
In-Reply-To: <209120000.997036451@tiny>
Chris Mason <mason@suse.com> writes:
> On Wednesday, August 01, 2001 04:57:35 PM +0200 Daniel Phillips
> <phillips@bonn-fries.net> wrote:
>
> > On Tuesday 31 July 2001 21:07, Chris Mason wrote:
> >> This has been tested a little more now, both ext2 (1k, 4k) and
> >> reiserfs. dbench and iozone testing don't show any difference, but I
> >> need to spend a little more time on the benchmarks.
> >
> > It's impressive that such seemingly radical surgery on the vm innards
> > is a) possible and b) doesn't make the system perform noticably worse.
>
> radical surgery is always possible ;-) But, I was expecting better
> performance results than I got. I'm trying a few other things out here,
> more details will come if they work.
Hmm. I would expect that could could entirely avoid the issue of which
hash chain to put pages on if you did the block devices in the page cache
thing. The the current buffer cache interface becomes just a
backwards compatibility layer which should make things cleaner.
Eric
next prev parent reply other threads:[~2001-08-06 15:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-05 18:34 [RFC] using writepage to start io Chris Mason
2001-08-05 22:38 ` Daniel Phillips
2001-08-05 23:32 ` Chris Mason
2001-08-06 5:39 ` Daniel Phillips
2001-08-06 13:24 ` Chris Mason
2001-08-06 16:13 ` Daniel Phillips
2001-08-06 16:51 ` Chris Mason
2001-08-06 19:45 ` Daniel Phillips
2001-08-06 20:12 ` Chris Mason
2001-08-06 21:18 ` Daniel Phillips
2001-08-07 11:02 ` Stephen C. Tweedie
2001-08-07 11:39 ` Ed Tomlinson
2001-08-07 18:36 ` Daniel Phillips
2001-08-07 12:07 ` Anton Altaparmakov
2001-08-07 12:02 ` Anton Altaparmakov
2001-08-07 13:29 ` Daniel Phillips
2001-08-07 13:31 ` Alexander Viro
2001-08-07 15:52 ` Daniel Phillips
2001-08-07 14:23 ` Stephen C. Tweedie
2001-08-07 15:51 ` Daniel Phillips
2001-08-08 14:49 ` Stephen C. Tweedie
2001-08-06 15:13 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-07 15:19 Chris Mason
2001-07-28 16:01 Chris Mason
2001-07-28 16:18 ` Alexander Viro
2001-07-28 16:25 ` Chris Mason
2001-07-31 19:07 ` Chris Mason
2001-08-01 1:01 ` Daniel Phillips
2001-08-01 2:05 ` Chris Mason
2001-08-01 14:57 ` Daniel Phillips
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=m11ympw7an.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mason@suse.com \
--cc=phillips@bonn-fries.net \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).