From: Amit Gud <amitgud@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Chris Wedgwood <cw@f00f.org>, linux-kernel@vger.kernel.org, gud@eth.net
Subject: Re: Using filesystem blocks
Date: Fri, 3 Sep 2004 17:36:40 +0530 [thread overview]
Message-ID: <2c6b3ab004090305061c6f1a59@mail.gmail.com> (raw)
In-Reply-To: <20040903091926.B2288@infradead.org>
> > First up, why is mbcache code is written at VFS layer than being
> > filesystem specific? Neccessarily to take away the coding overheads of
> > maintaining block cache that any filesystem uses, even though given
> > that only ext2 and ext3 uses it. It facilitates code reuse.
>
> It is not written at the VFS level. It's a library ontop of the buffercache
> than can be reused by filesystems.
>
Nice to know this. But intent of my mail is not affected by this in a major way.
AG
prev parent reply other threads:[~2004-09-03 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 19:29 Using filesystem blocks Amit Gud
2004-09-02 20:07 ` Chris Wedgwood
2004-09-03 4:56 ` Amit Gud
2004-09-03 8:19 ` Christoph Hellwig
2004-09-03 12:06 ` Amit Gud [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=2c6b3ab004090305061c6f1a59@mail.gmail.com \
--to=amitgud@gmail.com \
--cc=cw@f00f.org \
--cc=gud@eth.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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