From: Trond Myklebust <trond.myklebust@primarydata.com>
To: linux-nfs@vger.kernel.org
Subject: [PATCH v4 14/17] NFS: Cleanup nfs_direct_complete()
Date: Thu, 23 Jun 2016 16:00:46 -0400 [thread overview]
Message-ID: <1466712049-5326-14-git-send-email-trond.myklebust@primarydata.com> (raw)
In-Reply-To: <1466712049-5326-13-git-send-email-trond.myklebust@primarydata.com>
There is only one caller that sets the "write" argument to true,
so just move the call to nfs_zap_mapping() and get rid of the
now redundant argument.
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
---
fs/nfs/direct.c | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/fs/nfs/direct.c b/fs/nfs/direct.c
index 6d0e88096440..c16d33eb1ddf 100644
--- a/fs/nfs/direct.c
+++ b/fs/nfs/direct.c
@@ -372,13 +372,10 @@ out:
* Synchronous I/O uses a stack-allocated iocb. Thus we can't trust
* the iocb is still valid here if this is a synchronous request.
*/
-static void nfs_direct_complete(struct nfs_direct_req *dreq, bool write)
+static void nfs_direct_complete(struct nfs_direct_req *dreq)
{
struct inode *inode = dreq->inode;
- if (write)
- nfs_zap_mapping(inode, inode->i_mapping);
-
inode_dio_end(inode);
if (dreq->iocb) {
@@ -431,7 +428,7 @@ static void nfs_direct_read_completion(struct nfs_pgio_header *hdr)
}
out_put:
if (put_dreq(dreq))
- nfs_direct_complete(dreq, false);
+ nfs_direct_complete(dreq);
hdr->release(hdr);
}
@@ -537,7 +534,7 @@ static ssize_t nfs_direct_read_schedule_iovec(struct nfs_direct_req *dreq,
}
if (put_dreq(dreq))
- nfs_direct_complete(dreq, false);
+ nfs_direct_complete(dreq);
return 0;
}
@@ -764,7 +761,8 @@ static void nfs_direct_write_schedule_work(struct work_struct *work)
nfs_direct_write_reschedule(dreq);
break;
default:
- nfs_direct_complete(dreq, true);
+ nfs_zap_mapping(dreq->inode, dreq->inode->i_mapping);
+ nfs_direct_complete(dreq);
}
}
--
2.7.4
next prev parent reply other threads:[~2016-06-23 20:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 20:00 [PATCH v4 01/17] NFS: Don't flush caches for a getattr that races with writeback Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 02/17] NFS: Cache access checks more aggressively Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 03/17] NFS: Cache aggressively when file is open for writing Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 04/17] NFS: Kill NFS_INO_NFS_INO_FLUSHING: it is a performance killer Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 05/17] NFS: writepage of a single page should not be synchronous Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 06/17] NFS: Don't hold the inode lock across fsync() Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 07/17] NFS: Don't call COMMIT in ->releasepage() Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 08/17] NFS: Fix O_DIRECT verifier problems Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 09/17] NFS: Ensure we reset the write verifier 'committed' value on resend Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 10/17] NFS: Remove racy size manipulations in O_DIRECT Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 11/17] NFS Cleanup: move call to generic_write_checks() into fs/nfs/direct.c Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 12/17] NFS: Move buffered I/O locking into nfs_file_write() Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 13/17] NFS: Do not serialise O_DIRECT reads and writes Trond Myklebust
2016-06-23 20:00 ` Trond Myklebust [this message]
2016-06-23 20:00 ` [PATCH v4 15/17] NFS: Remove redundant waits for O_DIRECT in fsync() and write_begin() Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 16/17] NFS: Remove unused function nfs_revalidate_mapping_protected() Trond Myklebust
2016-06-23 20:00 ` [PATCH v4 17/17] NFS nfs_vm_page_mkwrite: Don't freeze me, Bro Trond Myklebust
2016-06-28 12:12 ` [PATCH v4 01/17] NFS: Don't flush caches for a getattr that races with writeback Christoph Hellwig
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=1466712049-5326-14-git-send-email-trond.myklebust@primarydata.com \
--to=trond.myklebust@primarydata.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).