From: Christoph Hellwig <hch@infradead.org>
To: tytso@mit.edu
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] [RFC] [PATCH 2/4] Add extended attributes to ext2/3
Date: Tue, 8 Oct 2002 19:23:06 +0100 [thread overview]
Message-ID: <20021008192306.B12912@infradead.org> (raw)
In-Reply-To: <E17yymE-00021l-00@think.thunk.org>; from tytso@mit.edu on Tue, Oct 08, 2002 at 02:08:14PM -0400
On Tue, Oct 08, 2002 at 02:08:14PM -0400, tytso@mit.edu wrote:
>
> This is the second of four patches which add extended attribute support
> to the ext2 and ext3 filesystems. Please comment and bleed.
>
> This patch creates a meta block cache which is utilized by the ext3 and
> ext2 extended attribute patch (patches 3 and 4, respectively). This
> cache allows directory blocks to be indexed by multiple keys. In the
> case of the extended attribute patches, it is used to look up blocks by
> both the block number and by the hash of the extended attributes. This
> is extremely important to allow the sharing of acl's when stored as
> extended attributes. Otherwise every single file would require its own,
> separate, one block overhead to store then ACL, even though there might
> be a large number of files that have the same ACL.
The code doesn't really make æny sense outside ext2/ext3. I'd suggest you
move it there instead of bloating every kernel with it unconditionally.
__mb_cache_entry_in_lru() is buggy and can't work anymore now that akpm removed
some list_head debugging.
And please get rid of the LINUX_VERSION_CODE checks..
next prev parent reply other threads:[~2002-10-08 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 18:08 [RFC] [PATCH 2/4] Add extended attributes to ext2/3 tytso
2002-10-08 18:23 ` Christoph Hellwig [this message]
2002-10-08 18:45 ` [Ext2-devel] " Theodore Ts'o
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=20021008192306.B12912@infradead.org \
--to=hch@infradead.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.