public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: andros@netapp.com
Cc: bfields@citi.umich.edu, linux-nfs@vger.kernel.org, pnfs@linux-nfs.org
Subject: Re: [pnfs] [PATCH 0/14] NFSv4.1 Server DRC rewrite Version 4
Date: Sun, 28 Jun 2009 19:01:04 +0300	[thread overview]
Message-ID: <4A4793C0.5040903@panasas.com> (raw)
In-Reply-To: <1245872278-18743-1-git-send-email-andros@netapp.com>

Andy,

I've merged this patchset onto the nfsd41 branch which
is now based on 2.6.31-rc1, replacing the respective patches
you sent previously.

Benny

On Jun. 24, 2009, 22:37 +0300, andros@netapp.com wrote:
> NFSv4.1 Server DRC rewrite Version 4
> 
> This patch set applies to linux-nfs.org/~bfields/linux, for-2.6.31 branch
> updated on 6-22-2009.
> 
> In response to bfield's comments I moved the DRC limit bug fixes to the front
> of the series, consolidated patches replacing the single slot clientid DRC
> into one patch and the replacement of the mulitple slot sequeqnce operation
> DRC into another single patch.
> 
> The NFSv4.1 DRC is changed from a page based cache to
> a buffer based cache. The logic for the single slot clientid cache has been
> separated from the session slot logic to handle the CREATE_SESSION call
> preceeded by a SEQUENCE and all the replay combinations therein.
> 
> The session DRC now caches encoded operations with the exception of the
> SEQUENCE operation which for a replay is encoded with the current slot and
> session values.  A review of message sizes indicates that a 512 byte buffer
> for the operations is adequate.
> 
> Not addressed is replacing the nfsd4_check_drc_limit() post-operation checking
> with a pre-operation processing estimate of the encoded per operation result
> 
> Testing:
> 4.1 mount: Connectathon and 4.1pynfs including the new create session replay
> tests.
> 4.0 mount; Connectathon.
> 
> 0001-nfsd41-use-globals-for-DRC-limits.patch
> 0002-nfsd41-change-from-page-to-memory-based-drc-limits.patch
> 0003-nfsd41-reclaim-DRC-memory-on-session-free.patch
> 0004-nfsd41-set-the-session-maximum-response-size-cached.patch
> 0005-nfsd41-remove-redundant-forechannel-max-requests-ch.patch
> 0006-nfsd41-change-check_slot_seqid-parameters.patch
> 0007-nfsd41-replace-create_session-DRC-with-xdr-structur.patch
> 0008-nfsd41-replace-page-based-DRC-with-buffer-based-DRC.patch
> 0009-nfsd41-rename-nfsd4_enc_uncached_replay.patch
> 0010-nfsd41-encode-replay-sequence-from-the-slot-values.patch
> 0011-nfsd41-fix-nfsd4_replay_cache_entry-comments.patch
> 0012-nfsd41-support-16-slots-per-session.patch
> 0013-nfsd41-add-test-for-failed-sequence-operation.patch
> 0014-nfsd41-remove-redundant-failed-sequence-check.patch
> 
> Comments welcome.
> 
> -->Andy
> 
> _______________________________________________
> pNFS mailing list
> pNFS@linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs

      parent reply	other threads:[~2009-06-28 16:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 19:37 [PATCH 0/14] NFSv4.1 Server DRC rewrite Version 4 andros
2009-06-24 19:37 ` [PATCH 1/5] nfsd41: use globals for DRC limits andros
2009-06-24 19:37   ` [PATCH 2/5] nfsd41: change from page to memory based drc limits andros
2009-06-24 19:37     ` [PATCH 3/5] nfsd41: reclaim DRC memory on session free andros
2009-06-24 19:37       ` [PATCH 4/5] nfsd41: set the session maximum response size cached andros
2009-06-24 19:37         ` [PATCH 5/5] nfsd41: remove redundant forechannel max requests check andros
2009-06-24 19:37           ` [PATCH 06/14] nfsd41: change check_slot_seqid parameters andros
2009-06-24 19:37             ` [PATCH 07/14] nfsd41: replace create_session DRC with xdr structure andros
2009-06-24 19:37               ` [PATCH 08/14] nfsd41: replace page based DRC with buffer based DRC andros
2009-06-24 19:37                 ` [PATCH 09/14] nfsd41: rename nfsd4_enc_uncached_replay andros
2009-06-24 19:37                   ` [PATCH 10/14] nfsd41: encode replay sequence from the slot values andros
2009-06-24 19:37                     ` [PATCH 11/14] nfsd41: fix nfsd4_replay_cache_entry comments andros
2009-06-24 19:37                       ` [PATCH 12/14] nfsd41: support 16 slots per session andros
2009-06-24 19:37                         ` [PATCH 13/14] nfsd41: add test for failed sequence operation andros
2009-06-24 19:37                           ` [PATCH 14/14] nfsd41: remove redundant failed sequence check andros
2009-07-01 23:09         ` [pnfs] [PATCH 4/5] nfsd41: set the session maximum response sizecached Alexandros Batsakis
2009-07-06 19:27           ` Andy Adamson
2009-07-06 21:48             ` J. Bruce Fields
2009-07-16 14:18       ` [pnfs] [PATCH 3/5] nfsd41: reclaim DRC memory on session free J. Bruce Fields
2009-07-16 15:49         ` William A. (Andy) Adamson
2009-07-27 22:57         ` J. Bruce Fields
2009-07-31  8:38           ` Andy Adamson
2009-07-16 14:17     ` [pnfs] [PATCH 2/5] nfsd41: change from page to memory based drc limits J. Bruce Fields
2009-07-16 18:50       ` J. Bruce Fields
2009-07-16 14:24     ` J. Bruce Fields
2009-06-28 16:01 ` Benny Halevy [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=4A4793C0.5040903@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=andros@netapp.com \
    --cc=bfields@citi.umich.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox