From: Mark Fasheh <mark.fasheh@oracle.com>
To: Steve French <smfltc@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] [PATCH] OCFS2
Date: Tue, 21 Jun 2005 17:04:43 -0700 [thread overview]
Message-ID: <20050622000442.GB7531@ca-server1.us.oracle.com> (raw)
In-Reply-To: <1119393793.5690.170.camel@stevef95.austin.ibm.com>
On Tue, Jun 21, 2005 at 05:43:13PM -0500, Steve French wrote:
> The list is not wrong. I was just noting that it was too short, missing
> three items of particular interest for server filesystems (which seems
> to be the target environment). Support for:
> Directory change notification (F_NOTIFY)
> Distributed Caching (F_SETLEASE/F_GETLEASE/break_lease)
> POSIX ACLs
Ahh, it seems I misread your earlier e-mail! In any case, I'll add those to
the list of missing features.
> The lack of support for lsattr/chattr (chflags) is less important, and
> the lack of support for the multipage operations (writepages and
> readpages) is not a compatability issue and is not critical, although it
> might hurt performance.
Yeah, I'm not sure how high a priority chflags are right now. Keeping in
mind that I'm mostly ignorant of cifs / samba, is there a particular set of
attributes there that it likes to use?
I'll have to look into why we don't currently support readpages /
writepages. I'm guessing it boiled down to lack of developer time :)
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com
next prev parent reply other threads:[~2005-06-22 0:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 21:14 [RFC] [PATCH] OCFS2 Steve French
2005-06-21 22:03 ` Mark Fasheh
2005-06-21 22:43 ` Steve French
2005-06-22 0:04 ` Mark Fasheh [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-18 22:33 Mark Fasheh
2005-05-18 23:35 ` Hans Reiser
2005-05-18 23:40 ` Adrian Bunk
2005-05-19 2:30 ` Kyle Moffett
2005-05-19 4:30 ` Mark Fasheh
2005-05-19 6:30 ` Daniel Phillips
2005-05-19 6:54 ` Mark Fasheh
2005-05-19 16:23 ` Daniel Phillips
2005-05-19 10:26 ` Jeff Garzik
2005-05-19 15:20 ` Lee Revell
2005-05-19 15:25 ` Jeff Garzik
2005-06-23 18:03 ` James Morris
2005-06-23 18:29 ` Mark Fasheh
2005-06-24 3:05 ` Paul Jackson
2005-06-24 3:29 ` Paul Jackson
2005-06-24 3:59 ` Mark Fasheh
2005-06-24 4:17 ` Paul Jackson
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=20050622000442.GB7531@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smfltc@us.ibm.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.