From: Chris Evans <chris@ferret.lmh.ox.ac.uk>
To: Roger Larsson <roger.larsson@norran.net>
Cc: "linux-kernel@vger.rutgers.edu" <linux-kernel@vger.rutgers.edu>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] page ageing with lists
Date: Thu, 13 Jul 2000 11:34:38 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.21.0007131129590.4769-100000@ferret.lmh.ox.ac.uk> (raw)
In-Reply-To: <396D1817.108394F5@norran.net>
On Thu, 13 Jul 2000, Roger Larsson wrote:
> Hi,
>
> This is a patch with page ageing for 2.4.0-test4-pre1.
>
> Performance, unoptimized filesystem:
> * streamed write is as good as 2.2.14
> * streamed copy is 3/4 of 2.2.14
> * streamed read is close to 2.2.14
Has anyone tested 2.4.0-test4-pre4 without any patches?
And shouldn't (in particular) streamed write be faster than 2.2 on account
of the unified buffer cache in 2.3?
Cheers
Chris
--
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/
prev parent reply other threads:[~2000-07-13 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-13 1:15 Roger Larsson
2000-07-13 10:34 ` Chris Evans [this message]
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=Pine.LNX.4.21.0007131129590.4769-100000@ferret.lmh.ox.ac.uk \
--to=chris@ferret.lmh.ox.ac.uk \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=roger.larsson@norran.net \
/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