From: "Nate Diller" <nate.diller@gmail.com>
To: "Hans Reiser" <reiser@namesys.com>
Cc: "Christoph Hellwig" <hch@infradead.org>,
"Alexander Zarochentsev" <zam@namesys.com>,
"Andrew Morton" <akpm@osdl.org>,
reiserfs-dev@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: partial reiser4 review comments
Date: Thu, 10 Aug 2006 11:31:46 -0700 [thread overview]
Message-ID: <5c49b0ed0608101131h55f1505eo44b78603e2e8d3c2@mail.gmail.com> (raw)
In-Reply-To: <44D9A86F.3010304@namesys.com>
On 8/9/06, Hans Reiser <reiser@namesys.com> wrote:
> Christoph Hellwig wrote:
>
> > I must admit that standalone code snipplet doesn't really tell me a lot.
> >
> >Do you mean the possibility to pass around a filesystem-defined structure
> >to multiple allocator calls? I'm pretty sure can add that, I though it
> >would be useful multiple times in the past but always found ways around
> >it.
> >
> >
> >
> Assuming I understand your discussion, I see two ways to go, one is to
> pass around fs specific state and continue to call into the FS many
> times, and the other is to instead provide the fs with helper functions
> that accomplish readahead calculation, page allocation, etc., and let
> the FS keep its state naturally without having to preserve it in some fs
> defined structure. The second approach would be cleaner code design,
> that would also ease cross-os porting of filesystems, in my view.
the second approach is the one i was heading towards with my
unfinished a_ops patches. *please* won't someone pay me to do that
work...
NATE
next prev parent reply other threads:[~2006-08-10 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:17 Andrew Morton
2006-08-03 14:26 ` Christoph Hellwig
2006-08-06 14:38 ` Alexander Zarochentsev
2006-08-09 8:59 ` Christoph Hellwig
2006-08-09 9:18 ` Hans Reiser
2006-08-10 18:31 ` Nate Diller [this message]
2006-08-11 17:55 ` Hans Reiser
2006-08-11 23:02 ` Nate Diller
2006-08-03 20:11 ` Alexander Zarochentsev
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=5c49b0ed0608101131h55f1505eo44b78603e2e8d3c2@mail.gmail.com \
--to=nate.diller@gmail.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-dev@namesys.com \
--cc=zam@namesys.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®