From: andros@netapp.com
To: bhalevy@panasas.com
Cc: iisaman@netapp.com, linux-nfs@vger.kernel.org,
Andy Adamson <andros@netapp.com>
Subject: [PATCH 01/10] SQUASHME pnfs_submit: remove filelayout get threshold
Date: Wed, 12 May 2010 10:44:13 -0400 [thread overview]
Message-ID: <1273675462-15758-2-git-send-email-andros@netapp.com> (raw)
In-Reply-To: <1273675462-15758-1-git-send-email-andros@netapp.com>
From: Andy Adamson <andros@netapp.com>
Prepare to remove unused threshold calculations
Squash into "pnfs:filelayout:policy ops"
Signed-off-by: Andy Adamson <andros@netapp.com>
---
fs/nfs/nfs4filelayout.c | 9 ---------
1 files changed, 0 insertions(+), 9 deletions(-)
diff --git a/fs/nfs/nfs4filelayout.c b/fs/nfs/nfs4filelayout.c
index 9d1274d..c2dda25 100644
--- a/fs/nfs/nfs4filelayout.c
+++ b/fs/nfs/nfs4filelayout.c
@@ -737,13 +737,6 @@ boundary:
return (p_stripe == r_stripe);
}
-ssize_t
-filelayout_get_io_threshold(struct pnfs_layout_type *layoutid,
- struct inode *inode)
-{
- return -1;
-}
-
struct layoutdriver_io_operations filelayout_io_operations = {
.commit = filelayout_commit,
.read_pagelist = filelayout_read_pagelist,
@@ -761,8 +754,6 @@ struct layoutdriver_policy_operations filelayout_policy_operations = {
PNFS_LAYOUTGET_ON_OPEN,
.get_stripesize = filelayout_get_stripesize,
.pg_test = filelayout_pg_test,
- .get_read_threshold = filelayout_get_io_threshold,
- .get_write_threshold = filelayout_get_io_threshold,
};
struct pnfs_layoutdriver_type filelayout_type = {
--
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 ` andros [this message]
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 ` [PATCH 08/10] SQUASHME pnfs_submit: don't use below_threshold in direct io andros
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-2-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).