From: Andrew Morton <akpm@digeo.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Hans Reiser <reiser@namesys.com>,
torvalds@transmeta.com, Nikita Danilov <Nikita@namesys.com>,
landley@trommello.org, linux-kernel@vger.kernel.org
Subject: Re: 2.5 merge candidate list, final version. (End of "crunch time"series.)
Date: Wed, 30 Oct 2002 01:35:31 -0800 [thread overview]
Message-ID: <3DBFA7E3.345690B2@digeo.com> (raw)
In-Reply-To: 3DBF9BA5.6000100@pobox.com
Jeff Garzik wrote:
>
> Hans Reiser wrote:
>
> > We are going to submit a patch appropriate for inclusion as an
> > experimental FS on Halloween. I hope you will forgive our pushing
> > the limit timewise, it is not by choice, but the algorithms we used to
> > more than double reiserfs V3 performance were, quite frankly, hard to
> > code.
>
> Does your merge change the core code at all? Does it add new syscalls?
>
Their changes are tiny, and sensible. See
http://www.namesys.com/snapshots/2002.10.29/
But I'd like to ask about the status of reiser3 support.
Chris had patches *ages* ago to convert it to use direct-to-BIO for
reads, and writes should be done as well. reiserfs3 is still using
buffer-head-based IO for bulk reads and writes. That's a 25-30% hit
in CPU cost, and all the old ZONE_NORMAL-full-of-buffer_heads
problems.
Any plans to get that work finished off?
next prev parent reply other threads:[~2002-10-30 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 11:34 2.5 merge candidate list, final version. (End of "crunch time" series.) Rob Landley
2002-10-28 16:55 ` Nikita Danilov
2002-10-29 12:28 ` Tomas Szepe
2002-10-30 8:19 ` Hans Reiser
2002-10-30 8:43 ` Jeff Garzik
2002-10-30 9:35 ` Andrew Morton [this message]
2002-10-30 10:15 ` 2.5 merge candidate list, final version. (End of "crunch time"series.) Nikita Danilov
2002-10-30 17:06 ` Chris Mason
2002-10-30 9:35 ` 2.5 merge candidate list, final version. (End of "crunch time" series.) Nikita Danilov
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=3DBFA7E3.345690B2@digeo.com \
--to=akpm@digeo.com \
--cc=Nikita@namesys.com \
--cc=jgarzik@pobox.com \
--cc=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--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