From: andros@netapp.com
To: bhalevy@panasas.com
Cc: iisaman@netapp.com, linux-nfs@vger.kernel.org,
Andy Adamson <andros@netapp.com>
Subject: [PATCH 08/10] SQUASHME pnfs_submit: don't use below_threshold in direct io
Date: Wed, 12 May 2010 10:44:20 -0400 [thread overview]
Message-ID: <1273675462-15758-9-git-send-email-andros@netapp.com> (raw)
In-Reply-To: <1273675462-15758-8-git-send-email-andros@netapp.com>
From: Andy Adamson <andros@netapp.com>
Prepare to remove unused threshold calculations
Squash into: "pnfs: Add function to set up O_DIRECT I/O"
Signed-off-by: Andy Adamon <andros@netapp.com>
---
fs/nfs/pnfs.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/fs/nfs/pnfs.c b/fs/nfs/pnfs.c
index 19cc193..9276bf8 100644
--- a/fs/nfs/pnfs.c
+++ b/fs/nfs/pnfs.c
@@ -1455,7 +1455,6 @@ _pnfs_direct_init_io(struct inode *inode, struct nfs_open_context *ctx,
unsigned int rwsize;
if (count <= 0 ||
- below_threshold(inode, count, iswrite) ||
pnfs_update_layout(inode, ctx, count, loff, IOMODE_READ, NULL))
return;
--
1.6.6
next prev parent reply other threads:[~2010-05-12 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 14:44 (unknown), andros
2010-05-12 14:44 ` [PATCH 01/10] SQUASHME pnfs_submit: remove filelayout get threshold andros
2010-05-12 14:44 ` [PATCH 02/10] SQUASHME pnfs_submit: don't use pnfs_use_read andros
2010-05-12 14:44 ` [PATCH 03/10] SQUASHME pnfs_submit: don't use pnfs_use_write andros
2010-05-12 14:44 ` [PATCH 04/10] SQUASHME pnfs_submit: don't use pnfs_use_write for commit andros
2010-05-12 14:44 ` [PATCH 05/10] SQUASHME pnfs_submit: don't use pg_threshold andros
2010-05-12 14:44 ` [PATCH 06/10] SQUASHME pnfs_submit: remove pg_threshold andros
2010-05-12 14:44 ` [PATCH 07/10] SQUASHME pnfs_submit: don't use below_threshold in read andros
2010-05-12 14:44 ` andros [this message]
2010-05-12 14:44 ` [PATCH 09/10] SQUASHME pnfs_submit: remove unused threshold calculations andros
2010-05-12 14:44 ` [PATCH 10/10] SQUASHME pnfs_submit: cleanup filelayout pg_test andros
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=1273675462-15758-9-git-send-email-andros@netapp.com \
--to=andros@netapp.com \
--cc=bhalevy@panasas.com \
--cc=iisaman@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).