public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Amit Gud <amitgud@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: gud@eth.net
Subject: Using filesystem blocks
Date: Fri, 3 Sep 2004 00:59:42 +0530	[thread overview]
Message-ID: <2c6b3ab004090212293b394b41@mail.gmail.com> (raw)

I don't know if this has been already discussed on the list before.

Is it wise enough to abstract away the usage of blocks for storing
extended attributes? I mean can the code  - of using filesystem
blocks, putting headers and all data in place within the blocks,
managing the block boundaries, padding ... - be taken away from within
the xattr code. I know xattr is filesystem specific, but if most of
filesystems are using blocks not associated with any inode to store
xattr-specifc information it could well be taken to a different layer
- just like mbcache. Almost only ext2/3 uses mbcache - and that too
only for xattr - but it is implemented at an abstract level.

Not only this would add to the modularization, this can help other
filesystems if they want to use filesystem blocks. Like if one wishes
to implement distributed filesystem, he may prefer to store the FS
metadata in blocks rather than in files. Is it advisible for him to
redo the code, which is very beautifully written in ext2/3 ? I think
not.

AG

             reply	other threads:[~2004-09-02 19:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02 19:29 Amit Gud [this message]
2004-09-02 20:07 ` Using filesystem blocks Chris Wedgwood
2004-09-03  4:56   ` Amit Gud
2004-09-03  8:19     ` Christoph Hellwig
2004-09-03 12:06       ` Amit Gud

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=2c6b3ab004090212293b394b41@mail.gmail.com \
    --to=amitgud@gmail.com \
    --cc=gud@eth.net \
    --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