All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: linux-nfs@vger.kernel.org
Subject: nfsd branch for 3.18
Date: Sun, 17 Aug 2014 16:06:52 -0400	[thread overview]
Message-ID: <20140817200652.GA24959@fieldses.org> (raw)

I've started a for-3.18 branch based on 3.17-rc1 which includes Trond's
scalability patches and a few other things:

	git://linux-nfs.org/~bfields/linux.git for-3.18

--b.

J. Bruce Fields (2):
      nfsd4: remove obsolete comment
      nfsd4: reserve adequate space for LOCK op

Jeff Layton (2):
      nfsd: protect lease-related nfs4_file fields with fi_lock
      nfsd: call nfs4_put_deleg_lease outside of state_lock

Ross Lagerwall (1):
      nfsd3: Check write permission after checking existence

Trond Myklebust (14):
      SUNRPC: Do not override wspace tests in svc_handle_xprt
      lockd: Ensure that lockd_start_svc sets the server rq_task...
      nfs: Ensure that nfs_callback_start_svc sets the server rq_task...
      SUNRPC: Do not grab pool->sp_lock unnecessarily in svc_get_next_xprt
      SUNRPC: get rid of the request wait queue
      SUNRPC: Fix broken kthread_should_stop test in svc_get_next_xprt
      SUNRPC: More optimisations of svc_xprt_enqueue()
      SUNRPC: Optimise away svc_recv_available
      nfsd: Clean up drc cache in preparation for global spinlock elimination
      nfsd: convert the lru list into a per-bucket thing
      nfsd: Remove the cache_hash list
      nfsd: convert num_drc_entries to an atomic_t
      nfsd: split DRC global spinlock into per-bucket locks
      nfsd: Reorder nfsd_cache_match to check more powerful discriminators first


                 reply	other threads:[~2014-08-17 20:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140817200652.GA24959@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 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.