From: Christoph Hellwig <hch@infradead.org>
To: Luka Renko <luka.renko@hermes.si>
Cc: Andreas Gruenbacher <agruen@suse.de>,
linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] [RFC] [PATCH 3/4] Add extended attributes to ext 2/3
Date: Wed, 9 Oct 2002 14:16:17 +0100 [thread overview]
Message-ID: <20021009141617.B22105@infradead.org> (raw)
In-Reply-To: <A1C30C1C0FB8D5118D810004754C03756677C5@hsl-lj3x.hermes.si>; from luka.renko@hermes.si on Wed, Oct 09, 2002 at 10:53:47AM +0200
On Wed, Oct 09, 2002 at 10:53:47AM +0200, Luka Renko wrote:
> Actually we are currently developing HSM application that stacks on top of
> standard file system (ext3 and XFS today) and we are using EA to store HSM
> specific information with each inode. However, we are not using registration
> API, but rather store this in user EA (even if we don't like some
> limitations of user EA), because registration API is not exported and
> registration API is per-FS and not generic. This would mean that we would
> need to have handlers defined for each supported filesystem (ext3 and XFS
> today, reiserfs and JFS in near future). As we use user EA, we just call VFS
> EA operations of the bottom FS (ext3 or XFS or any other FS that supports
> EA).
Yupp, that's exactly what I meant.
> I think that we could also then have only single ACL code for both ext2 and
> ext3 - currently ACL patch adds similar (same?) code to both ext2 and ext3
> and this code could be shared for sure.
And JFS and reiserfs. Yes, this code should be in a library, but e.g.
XFS (different ondisk format) or NFSv4/NTFS/whatever need very different
ACL rountines. You can't easily plug the handler into different filesystems
due to very different implementations below the VFS level.
BTW, do you have a pointer to your DSM system? I'l like to look at something
less broken them dmapi..
prev parent reply other threads:[~2002-10-09 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 8:53 Luka Renko
2002-10-09 13:16 ` Christoph Hellwig [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=20021009141617.B22105@infradead.org \
--to=hch@infradead.org \
--cc=agruen@suse.de \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luka.renko@hermes.si \
/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®