All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] xattr/acl support
Date: Thu Mar 31 07:44:33 2005	[thread overview]
Message-ID: <200503310844.30032.mason@suse.com> (raw)
In-Reply-To: <20050329193913.GA28010@ca-server1.us.oracle.com>

On Tuesday 29 March 2005 14:39, Joel Becker wrote:
> On Tue, Mar 29, 2005 at 12:19:19PM -0500, Chris Mason wrote:
> > ;) Does the disk format already have all the slots reserved for such a
> > thing? It looks like you've probably got some extra room on the end of
> > the inode, I'm hoping for something that can pack in tiny files directly
> > and perhaps store small acls/xattrs in there.
>
> 	We've not agreed yet on how we want to implement them.  We go
> back and forth.  Could be internal to the inode reserved space for a few
> small xattrs, expanding to a whole cluster for larger ones.  Or it could
> be block-based, copying the code directly from ext3.  We just haven't
> decided yet.

There's a real performance hit moving the common xattrs (especially acls) 
outside the inode.  I'd suggest storing at least some of them internally.

> 	Note that there is no extra room at the "end" of the inode, as
> the extent list fills to the end.  The extra room is in the reserved
> fields.

Ok, thanks.

-chris

      reply	other threads:[~2005-03-31  7:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29  8:04 [Ocfs2-devel] xattr/acl support Chris Mason
2005-03-29 10:04 ` Wim Coekaerts
2005-03-29 11:19   ` Chris Mason
2005-03-29 13:45     ` Joel Becker
2005-03-31  7:44       ` Chris Mason [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=200503310844.30032.mason@suse.com \
    --to=mason@suse.com \
    --cc=ocfs2-devel@oss.oracle.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 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.