All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Extended Attribute Support?
Date: Wed, 7 Jun 2006 09:45:19 -0700	[thread overview]
Message-ID: <20060607164519.GM3082@ca-server1.us.oracle.com> (raw)
In-Reply-To: <355a4e960606070435q69e1413fga5c30869d38caf31@mail.gmail.com>

On Wed, Jun 07, 2006 at 04:35:31AM -0700, EKC wrote:
> Any word on when extended attribute support will be added to OCFS2?
When we get to it ;) Seriously though, EA support is being planned for, it's
just lower on the priority list than things like sparse file support, online
resize, directory improvements, etc.

> What are the impediments to someone implementing this?
Not much - downloading the latest kernel code and editing fs/ocfs2/ to add
this :) Patches are always welcome, and actually I think EA is a good
candidate for someone who wants to contribute but doesn't yet understand the
all the cluster stuff.

As a first pass, a simple attribute block, pointed to by an __le64 in the
dinode would work fine. More improvements and optimizations could come after
that.

> I've been watching the open source Lustre fs development, too. I
> noticed that they have added extended attribute support. However,
> OCFS2 is more attractive for some applications.
Don't they get EA from ext3? Anyway, yeah Lustre does some really cool stuff
- I think we're pretty different in the types of clusters we serve though :)
	--Mark

--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh at oracle.com

  reply	other threads:[~2006-06-07 16:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 11:35 [Ocfs2-devel] Extended Attribute Support? EKC
2006-06-07 16:45 ` Mark Fasheh [this message]
2006-06-08  0:47   ` EKC
2006-06-08  3:46     ` Mark Fasheh
2006-06-08  4:43       ` EKC
2006-06-09  4:08         ` Mark Fasheh

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=20060607164519.GM3082@ca-server1.us.oracle.com \
    --to=mark.fasheh@oracle.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.