From: Benny Halevy <bhalevy@panasas.com>
To: Olga Kornievskaia <aglo@citi.umich.edu>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: question about nfs41 features
Date: Tue, 28 Sep 2010 11:27:15 +0200 [thread overview]
Message-ID: <4CA1B4F3.7030106@panasas.com> (raw)
In-Reply-To: <20100923210440.GC14610@fieldses.org>
On 2010-09-23 23:04, J. Bruce Fields wrote:
> On Thu, Sep 23, 2010 at 02:30:49PM -0400, Olga Kornievskaia wrote:
>> I would greatly appreciate it I can get a reply from NFS41 server
>> implementers out there on the subject of whether or not the following
>> feature are (a) currently implemented by your server, (b) will be
>> implemented soon (1year), (c) having interest in being implemented
>> within the next few years and (d) are so low in priority that could be
>> said: will never be implemented.
>
> This could change depending on interest, of course, but:
>
>> volatile handles
>> named attributes
>
> Probably both (d).
>
>> directory delegations
>> SSV
>
> I'm guessing (c) or (d). (I'd be happier if SSV were a higher priority,
> but oh well.)
>
>> trunking (session or clientid)
>
> (b)
>
>> segmented file layouts
>>
maybe (c)
>> recall of file layouts
>> cb_notify_deviceid
This is already implemented in the linux-pnfs tree.
Benny
>
> Not sure.
>
>> cb_getattr
>
> (c)
>
>> cb_recall_slot
>> cb_notify_lock
>
> Probably both (c).
>
> This list doesn't necessarily get you anyone other than linux
> implementors, so you may want to ask on nfsv4@ietf.org or ask people at
> the bakeathon.
>
> --b.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-09-28 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 18:30 question about nfs41 features Olga Kornievskaia
2010-09-23 21:04 ` J. Bruce Fields
2010-09-23 21:09 ` Olga Kornievskaia
2010-09-28 9:27 ` Benny Halevy [this message]
2010-09-23 21:31 ` Mkrtchyan, Tigran
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=4CA1B4F3.7030106@panasas.com \
--to=bhalevy@panasas.com \
--cc=aglo@citi.umich.edu \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.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.