public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: linux-nfs@vger.kernel.org
Subject: misc (mostly callback) patches for 2.6.31
Date: Sun,  3 May 2009 14:16:26 -0400	[thread overview]
Message-ID: <1241374599-20348-1-git-send-email-bfields@fieldses.org> (raw)


I intend to submit the following for 2.6.31, mainly concerned with
moving the nfsv4 callbacks to asynchronous rpc's.  Currently we create a
new kthread for each callback.  But there's no real reason they need a
real thread, and I'm assuming an rpc task will be lighter-weight.  This
should also keep the callbacks from outliving the nfsd module (though
that could probably be solved some other way).

Next I'd like to improve the decision about when to declare the callback
channel down, and implement the callback-parameter-changing case of
setclientid (and the corresponding 4.1 case).  For the latter I'm
currently stuck trying to decide how to do the locking necessary to
prevent races between destruction of the old rpc client and
lease-breaking code about to launch a new rpc task using the old rpc
client.

--b.

             reply	other threads:[~2009-05-03 18:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-03 18:16 J. Bruce Fields [this message]
2009-05-03 18:16 ` [PATCH] nfsd4: rename callback struct to cb_conn J. Bruce Fields
2009-05-03 18:16   ` [PATCH] nfsd: quiet compile warning J. Bruce Fields
2009-05-03 18:16     ` [PATCH] nfsd4: setclientid_confirm callback-change fixes J. Bruce Fields
2009-05-03 18:16       ` [PATCH] nfsd4: set shorter timeout J. Bruce Fields
2009-05-03 18:16         ` [PATCH] nfsd4: set cb_client inside setup_callback_client J. Bruce Fields
2009-05-03 18:16           ` [PATCH] nfsd4: create rpc callback client from server thread J. Bruce Fields
2009-05-03 18:16             ` [PATCH] nfsd4: lookup up callback cred only once J. Bruce Fields
2009-05-03 18:16               ` [PATCH] nfsd4: replace callback thread by asynchronous rpc J. Bruce Fields
2009-05-03 18:16                 ` [PATCH] nfsd4: rename callback struct to cb_conn J. Bruce Fields
2009-05-03 18:16                   ` [PATCH] nfsd4: eliminate struct nfs4_cb_recall J. Bruce Fields
2009-05-03 18:16                     ` [PATCH] nfsd4: remove unused dl_trunc J. Bruce Fields
2009-05-03 18:16                       ` [PATCH] nfsd4: track recall retries in nfs4_delegation J. Bruce Fields
2009-05-03 18:16                         ` [PATCH] nfsd4: make recall callback an asynchronous rpc 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=1241374599-20348-1-git-send-email-bfields@fieldses.org \
    --to=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