From: Boaz Harrosh <bharrosh@panasas.com>
To: Benny Halevy <bhalevy@tonian.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
<lsf-pc@lists.linux-foundation.org>,
<linux-fsdevel@vger.kernel.org>,
NFS list <linux-nfs@vger.kernel.org>,
"J. Bruce Fields" <bfields@redhat.com>,
Jeff Layton <jlayton@redhat.com>
Subject: Re: [LSF/MM TOPIC] [ATTEND] linux-pnfs server implementations
Date: Wed, 11 Jan 2012 15:28:53 +0200 [thread overview]
Message-ID: <4F0D8E95.60706@panasas.com> (raw)
In-Reply-To: <CAEMWVhvaNOENPC2jRMB7zuP4ScsNmp5BMfXYmnFL71_N-4D0Rw@mail.gmail.com>
On 01/11/2012 09:44 AM, Benny Halevy wrote:
>>
>> Understood that it may depend on where things stand in April, but: what
>> specifically do you think will be likely to require the attention of a
>> wider group of linux filesystem developers (ass opposed to just nfs
>> developers)?
>
> I have nothing specific at this time. My thinking was to present the
> what's and why's
> of the prerequisites in high level and maybe provide an example.
>
At the time there where some reservations from people about some of the
added hooks and vectors. If there are still, we would like to hear them
and either address them or argue their validity.
I think this talk should be expanded with Jeff's suggestions. here:
> - RichACLs
> - Share/Deny mode support on open
> - mandatory locking that doesn't rely on weirdo file modes
>
> It's always going to be hard for us to compete with dedicated
> appliances. Where Linux can shine though is in allowing for more
> innovative combinations.
>
> Being able to do active/active NFS serving from clustered filesystems,
> for instance is something that we can eventually attain but that would
> be harder to do in an appliance. This sort of discussion might also
> dovetail with Benny's proposal about pNFS serving.
So the broader topic can be:
"The things we want/need from the Kernel to make it exportable"
Thanks
Boaz
next prev parent reply other threads:[~2012-01-11 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-25 4:30 [LSF/MM TOPIC] [ATTEND] linux-pnfs server implementations Benny Halevy
2011-12-25 4:30 ` Benny Halevy
2012-01-09 12:49 ` Boaz Harrosh
2012-01-09 19:25 ` J. Bruce Fields
2012-01-11 7:44 ` Benny Halevy
2012-01-11 7:44 ` Benny Halevy
2012-01-11 13:28 ` Boaz Harrosh [this message]
2012-01-11 14:11 ` J. Bruce Fields
2012-01-11 14:11 ` J. Bruce Fields
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=4F0D8E95.60706@panasas.com \
--to=bharrosh@panasas.com \
--cc=bfields@fieldses.org \
--cc=bfields@redhat.com \
--cc=bhalevy@tonian.com \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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.