All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: andros@netapp.com
Cc: linux-nfs@vger.kernel.org, pnfs@linux-nfs.org
Subject: Re: [pnfs] [PATCH 0/5] NFSv4.1 DRC rewrite version 6
Date: Fri, 28 Aug 2009 19:07:27 -0400	[thread overview]
Message-ID: <20090828230727.GI2462@fieldses.org> (raw)
In-Reply-To: <20090828225608.GH2462@fieldses.org>

On Fri, Aug 28, 2009 at 06:56:08PM -0400, bfields wrote:
> On Fri, Aug 28, 2009 at 06:42:48PM -0400, J. Bruce Fields wrote:
> > On Thu, Aug 27, 2009 at 12:07:39PM -0400, andros@netapp.com wrote:
> > > 
> > > NFSv4.1 DRC Rewrite Version 6
> > > 
> > > These patches apply against git://linux-nfs.org/~bfields/linux: for-2.6.32
> > > branch and continue to rewrite the NFSv4.1 Sessions DRC. Besides some
> > > bug fixes:
> > > 
> > > 1) The bound on the fore channel per-session DRC size are rewritten.
> > > Instead of just using a maximum number of slots to bound the size,
> > > The server gives the client the number of ca_maxresponsesize_cached slots it
> > > requests bounded by NFSD_SLOT_CACHE_SIZE, NFSD_MAX_MEM_PER_SESSION and by
> > > nfsd_drc_max_mem. Do not allow more than NFSD_MAX_SLOTS_PER_SESSION.
> > > 
> > > This allows clients to tailor a session to usage.
> > > For example, an I/O session (READ/WRITE/COMMIT only) can have a much smaller
> > > ca_maxresponsesize_cached (for only WRITE/COMMIt compound responses) and a lot
> > > larger ca_maxresponses to service a large in-flight data window.
> > > 
> > > 2) the page-based DRC is replaced with a buffer based DRC with each
> > > slot table entry (struct nfsd4_slot + cache) allocated separately.
> > > This allocation prepares us for slot size re-negotiation via the SEQUENCE
> > > operation target and high slot id arguments.
> > > 
> > > Testing:
> > > 
> > > NFSv4.1 mount: pynfs tests - including the SEQUENCE replay cache tests.
> > > connectathon tests.
> > 
> > By the way, any hints on getting the 4.1 pynfs stuff running?
> 
> OK, solution seemed to be
> 
> 	cd gssapi
> 	python setup.py build_ext --inplace
> 
> But now almost everything fails.with SERVERFAULT.  Bah.

Does anyone have a list of which tests are expected to pass at this point?  If
I ask for "all" tests, I get "4 skipped, 103 failed, 0 warned, 26 passed--full
list available if anyone wants.  I seem to be passing connectathon tests
OK over 4.1.

--b.

  reply	other threads:[~2009-08-28 23:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27 16:07 [PATCH 0/5] NFSv4.1 DRC rewrite version 6 andros
2009-08-27 16:07 ` [PATCH 1/5] nfsd41: expand solo sequence check andros
2009-08-27 16:07   ` [PATCH 2/5] nfsd41: bound forechannel drc size by memory usage andros
2009-08-27 16:07     ` [PATCH 3/5] nfsd41: use session maxreqs for sequence target and highest slotid andros
2009-08-27 16:07       ` [PATCH 4/5] nfsd41: replace nfserr_resource in pure nfs41 responses andros
2009-08-27 16:07         ` [PATCH 5/5] nfsd41: replace page based DRC with buffer based DRC andros
2009-08-28 21:33           ` J. Bruce Fields
2009-08-30 23:10             ` [pnfs] " Benny Halevy
2009-08-31 13:08               ` J. Bruce Fields
2009-08-31 13:43                 ` William A. (Andy) Adamson
2009-09-01 13:48             ` William A. (Andy) Adamson
     [not found]               ` <89c397150909010648v4a4f5db8t87e09717e5a2c950-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-01 15:14                 ` J. Bruce Fields
2009-09-01 15:22                   ` William A. (Andy) Adamson
2009-08-27 17:12     ` [PATCH 2/5] nfsd41: bound forechannel drc size by memory usage William A. (Andy) Adamson
2009-08-28 20:41     ` J. Bruce Fields
2009-08-28 20:56       ` J. Bruce Fields
2009-08-30  6:38       ` [pnfs] " Benny Halevy
2009-08-27 21:42   ` [PATCH 1/5] nfsd41: expand solo sequence check J. Bruce Fields
2009-08-28 21:34 ` [PATCH 0/5] NFSv4.1 DRC rewrite version 6 J. Bruce Fields
2009-08-28 22:42 ` J. Bruce Fields
2009-08-28 22:56   ` [pnfs] " J. Bruce Fields
2009-08-28 23:07     ` J. Bruce Fields [this message]
2009-09-08 14:43       ` 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=20090828230727.GI2462@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.