From: <Anna.Schumaker@Netapp.com>
To: <linux-nfs@vger.kernel.org>
Subject: [PATCH 00/11] Create a single nfs4_setup_sequence() function
Date: Wed, 11 Jan 2017 13:54:43 -0500 [thread overview]
Message-ID: <20170111185454.9315-1-Anna.Schumaker@Netapp.com> (raw)
From: Anna Schumaker <Anna.Schumaker@Netapp.com>
I noticed that NFS v4.0 and v4.1 have different setup_sequence() functions
that are very, very similar. I think we should try to share as much code
as possible whenever possible, so these patches merge together both versions
of this function using the presence of a session to decide if we need to do
a little extra work in some cases.
I broke this change into several logical steps that (hopefully) make it easier
to follow what I did.
Questions? Comments? Thoughts?
Anna
Anna Schumaker (11):
NFS: Move nfs4_get_session() into nfs4_session.h
NFS: Change nfs4_get_session() to take an nfs_client structure
NFS: Change nfs4_setup_sequence() to take an nfs_client structure
NFS: Use nfs4_setup_sequence() everywhere
NFS: Create a single nfs4_setup_sequence() function
NFS: Move slot-already-allocated check into nfs_setup_sequence()
NFS: Lock the slot table from a single place during setup sequence
NFS: Handle setup sequence task rescheduling in a single place
NFS: Check if the slot table is draining from nfs4_setup_sequence()
NFS: Merge the remaining setup_sequence functions
NFS: Make trace_nfs4_setup_sequence() available to NFS v4.0
fs/nfs/filelayout/filelayout.c | 6 +-
fs/nfs/flexfilelayout/flexfilelayout.c | 40 ++----
fs/nfs/nfs42proc.c | 6 +-
fs/nfs/nfs4_fs.h | 15 +-
fs/nfs/nfs4proc.c | 244 +++++++++++----------------------
fs/nfs/nfs4session.h | 7 +
fs/nfs/nfs4trace.h | 64 ++++-----
7 files changed, 139 insertions(+), 243 deletions(-)
--
2.11.0
next reply other threads:[~2017-01-11 18:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 18:54 Anna.Schumaker [this message]
2017-01-11 18:54 ` [PATCH 01/11] NFS: Move nfs4_get_session() into nfs4_session.h Anna.Schumaker
2017-01-11 18:54 ` [PATCH 02/11] NFS: Change nfs4_get_session() to take an nfs_client structure Anna.Schumaker
2017-01-11 18:54 ` [PATCH 03/11] NFS: Change nfs4_setup_sequence() " Anna.Schumaker
2017-01-11 18:54 ` [PATCH 04/11] NFS: Use nfs4_setup_sequence() everywhere Anna.Schumaker
2017-01-11 18:54 ` [PATCH 05/11] NFS: Create a single nfs4_setup_sequence() function Anna.Schumaker
2017-01-11 18:54 ` [PATCH 06/11] NFS: Move slot-already-allocated check into nfs_setup_sequence() Anna.Schumaker
2017-01-11 18:54 ` [PATCH 07/11] NFS: Lock the slot table from a single place during setup sequence Anna.Schumaker
2017-01-11 18:54 ` [PATCH 08/11] NFS: Handle setup sequence task rescheduling in a single place Anna.Schumaker
2017-01-11 18:54 ` [PATCH 09/11] NFS: Check if the slot table is draining from nfs4_setup_sequence() Anna.Schumaker
2017-01-11 18:54 ` [PATCH 10/11] NFS: Merge the remaining setup_sequence functions Anna.Schumaker
2017-01-11 18:54 ` [PATCH 11/11] NFS: Make trace_nfs4_setup_sequence() available to NFS v4.0 Anna.Schumaker
2017-01-11 18:57 ` [PATCH 00/11] Create a single nfs4_setup_sequence() function Chuck Lever
2017-01-11 19:13 ` Anna Schumaker
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=20170111185454.9315-1-Anna.Schumaker@Netapp.com \
--to=anna.schumaker@netapp.com \
--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;
as well as URLs for NNTP newsgroup(s).