From: Theodore Ts'o <tytso@mit.edu>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Cc: Theodore Ts'o <tytso@mit.edu>, Jiaying Zhang <jiayingz@google.com>
Subject: [PATCH v4 3/3] ext4: Use direct_IO_no_locking in ext4 dio read.
Date: Fri, 15 Jan 2010 14:30:12 -0500 [thread overview]
Message-ID: <1263583812-21355-4-git-send-email-tytso@mit.edu> (raw)
In-Reply-To: <1263583812-21355-1-git-send-email-tytso@mit.edu>
Signed-off-by: Jiaying Zhang <jiayingz@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
---
fs/ext4/inode.c | 9 ++++++++-
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
index 1f56484..ec0bbdd 100644
--- a/fs/ext4/inode.c
+++ b/fs/ext4/inode.c
@@ -3419,7 +3419,14 @@ static ssize_t ext4_ind_direct_IO(int rw, struct kiocb *iocb,
}
retry:
- ret = blockdev_direct_IO(rw, iocb, inode, inode->i_sb->s_bdev, iov,
+ if (rw == READ && ext4_should_dioread_nolock(inode))
+ ret = blockdev_direct_IO_no_locking(rw, iocb, inode,
+ inode->i_sb->s_bdev, iov,
+ offset, nr_segs,
+ ext4_get_block, NULL);
+ else
+ ret = blockdev_direct_IO(rw, iocb, inode,
+ inode->i_sb->s_bdev, iov,
offset, nr_segs,
ext4_get_block, NULL);
if (ret == -ENOSPC && ext4_should_retry_alloc(inode->i_sb, &retries))
--
1.6.5.216.g5288a.dirty
next prev parent reply other threads:[~2010-01-15 19:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 19:30 [PATCH v4 0/3] dioread_nolock patch Theodore Ts'o
2010-01-15 19:30 ` [PATCH v4 1/3] ext4: mechanical change on dio get_block code in prepare for it to be used by buffer write Theodore Ts'o
2010-01-17 14:36 ` Aneesh Kumar K. V
2010-01-17 16:19 ` Eric Sandeen
2010-01-17 16:42 ` Aneesh Kumar K. V
2010-01-18 3:57 ` tytso
2010-01-15 19:30 ` [PATCH v4 2/3] ext4: use ext4_get_block_write in " Theodore Ts'o
2010-01-16 2:17 ` tytso
2010-01-17 14:21 ` Aneesh Kumar K. V
2010-01-18 5:25 ` Jiaying Zhang
2010-01-15 19:30 ` Theodore Ts'o [this message]
2010-01-17 14:19 ` [PATCH v4 3/3] ext4: Use direct_IO_no_locking in ext4 dio read Aneesh Kumar K. V
2010-01-15 19:39 ` [PATCH v4 0/3] dioread_nolock patch Ric Wheeler
2010-01-15 19:52 ` Eric Sandeen
2010-01-15 20:15 ` tytso
2010-01-15 20:17 ` Eric Sandeen
2010-01-15 21:47 ` Michael Rubin
2010-01-22 20:47 ` Valerie Aurora
2010-02-20 0:56 ` Michael Rubin
2010-02-23 0:36 ` Andreas Dilger
2010-02-16 21:07 ` Darrick J. Wong
2010-02-17 19:34 ` Jiaying Zhang
2010-02-19 21:25 ` Darrick J. Wong
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=1263583812-21355-4-git-send-email-tytso@mit.edu \
--to=tytso@mit.edu \
--cc=jiayingz@google.com \
--cc=linux-ext4@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).