All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: andros@netapp.com
Cc: pnfs@linux-nfs.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/2] nfsd41: fix fore channel attribute initialization
Date: Mon, 14 Sep 2009 14:54:42 -0400	[thread overview]
Message-ID: <20090914185442.GC1658@fieldses.org> (raw)
In-Reply-To: <1252709575-3426-1-git-send-email-andros@netapp.com>

On Fri, Sep 11, 2009 at 06:52:53PM -0400, andros@netapp.com wrote:
> Fix forechannel attribute initialization
> 
> These two patches fix ca_maxresponsesize_cached, ca_maxresponsesize, and
> ca_maxrequestsize calculations for the forechannel.
> 
> Tested:

Actually the think I was interested to test was just to make sure that
the client does writes of the size it should.  (It should be able to do
1MB reads and writes, but with the previous code, I believe it would
have been a bug for the client to do so, as we weren't advertising
maxresponse/requestsizes large enough.)

--b.

> 
> Kerberos NFSv4.1 mount:
> Passes Connectathon tests. Passes the expected pynfs tests when tests are run
> individually.
> When the pynfs tests are run all at once, there are too many sessions created,
> and the server code (init_forechannel_attrs) works as planned and fails the
> CREATE SESSION with NFS4ERR_SERVERFAULT.
> 
> The pynfs 4.1 tests need to be fixed to clean up after themselves! 
> 
> -->Andy
> 
> 0001-nfsd41-fix-NFSD_MIN_HDR_SEQ_SZ.patch
> 0002-nfsd41-add-RPC-header-size-to-fore-channel-negotiat.patch
> 

      parent reply	other threads:[~2009-09-14 18:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 22:52 [PATCH 0/2] nfsd41: fix fore channel attribute initialization andros
2009-09-11 22:52 ` [PATCH 1/2] nfsd41: fix NFSD_MIN_HDR_SEQ_SZ andros
2009-09-11 22:52   ` [PATCH 2/2] nfsd41: add RPC header size to fore channel negotiation andros
2009-09-14 19:03     ` J. Bruce Fields
2009-09-18 16:47       ` [pnfs] " William A. (Andy) Adamson
     [not found]         ` <89c397150909180947w69b0139dx732100109e2793b0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-18 21:12           ` J. Bruce Fields
2009-09-21 12:29             ` William A. (Andy) Adamson
     [not found]               ` <89c397150909210529q5b119d9dmff958dfe2d859635-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-21 21:20                 ` J. Bruce Fields
2009-09-14 18:51   ` [PATCH 1/2] nfsd41: fix NFSD_MIN_HDR_SEQ_SZ J. Bruce Fields
2009-09-14 20:11     ` [pnfs] " William A. (Andy) Adamson
2009-09-14 18:54 ` J. Bruce Fields [this message]

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=20090914185442.GC1658@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=andros@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=pnfs@linux-nfs.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.