From: Tom Tucker <tom@ogc.us>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfsd (and lock) changes for 3.2
Date: Tue, 25 Oct 2011 23:41:43 -0500 [thread overview]
Message-ID: <4EA78F87.2050109@ogc.us> (raw)
In-Reply-To: <20111025123449.GB15662@fieldses.org>
Hi Bruce,
What does RDMA Non Support mean exactly? Maybe I could help if it's a
resource issue?
Thanks,
Tom
On 10/25/11 7:34 AM, J. Bruce Fields wrote:
> On Tue, Oct 25, 2011 at 08:19:24AM -0400, bfields wrote:
>> - Progress on the basic 4.1 todo's. Thanks in particular to Mi
>> Jinlong for (among other things) implementing the somewhat
>> tricky DRC limit checking.
>>
>> The 4.1 code is getting closer--it *might* be possible to
>> finish basic 4.1 early as 3.3, at which point we could start
>> on optional features (like pNFS). But that will depend on
>> people sending patches (and pynfs tests) for the remaining 4.1
>> todo's.
> I've been keeping the todo list up to date here:
>
> http://wiki.linux-nfs.org/wiki/index.php/Server_4.0_and_4.1_issues
>
> Some of them I think are relatively straightforward--probably anyone
> with a little time could dive into them:
>
> - SEQ4_STATUS_RECALLABLE_STATE_REVOKED
>
> - backchannel attribute negotiation
>
> - ACL retention bits
>
> - Clarify RDMA non-support
>
> Slightly trickier or open-ended; we may need to talk over design first
> before diving in:
>
> - Make DESTROY_SESSION wait on in-progress requests
>
> - current stateid
>
> - Check 4.0/4.1 interactions
>
> - Callback failure handling
>
> - GSS
>
> The GSS piece is probably the one I'm most worried about. What we have
> seems sufficient for current clients, but I know it's incomplete, and
> I'm not entirely clear how much work it is to implement the minimum
> required to ensure that future kerberos-using clients won't break
> unexpectedly on upgrade to 4.1.
>
> --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:[~2011-10-26 4:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 12:19 nfsd (and lock) changes for 3.2 J. Bruce Fields
2011-10-25 12:34 ` J. Bruce Fields
2011-10-26 4:41 ` Tom Tucker [this message]
2011-10-26 8:59 ` J. Bruce Fields
2011-10-26 3:16 ` Boaz Harrosh
2011-10-26 3:31 ` Boaz Harrosh
2011-10-27 20:34 ` J. Bruce Fields
2011-10-28 0:23 ` Boaz Harrosh
2011-10-28 14:42 ` J. Bruce Fields
2011-11-04 16:04 ` J. Bruce Fields
2011-11-04 16:50 ` Boaz Harrosh
2011-11-04 17:45 ` J. Bruce Fields
2011-11-07 16:21 ` Benny Halevy
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=4EA78F87.2050109@ogc.us \
--to=tom@ogc.us \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).