From: Nikita Danilov <Nikita@Namesys.COM>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Hans Reiser <reiser@namesys.com>,
torvalds@transmeta.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 12:35:56 +0300 [thread overview]
Message-ID: <15807.43004.24713.813565@laputa.namesys.com> (raw)
In-Reply-To: <3DBF9BA5.6000100@pobox.com>
Jeff Garzik writes:
> 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?
>
Here is a list of things reiser4 needs from the core:
(1) export of generic_forget_inode()
(2) export of page_cache_readahead()
(3) export of remove_from_page_cache()
(4) export of fsync_super()
(5) patch to allow safe sharing of ->journal_info pointer in task_struct
by several users
(1)-(4) are only necessary to compile reiser4 as module.
(5) is good not only for reiser4. Without it different file systems
using ->journal_info cannot "co-exist peacefully".
No new system calls are introduced (yet).
Nikita.
>
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 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 ` 2.5 merge candidate list, final version. (End of "crunch time"series.) Andrew Morton
2002-10-30 10:15 ` Nikita Danilov
2002-10-30 17:06 ` Chris Mason
2002-10-30 9:35 ` Nikita Danilov [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=15807.43004.24713.813565@laputa.namesys.com \
--to=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
all inboxes | Powered by JetHome®