From: Michael Trimarchi <trimarchimichael@yahoo.it>
To: Martin Knoblauch <knobi@knobisoft.de>,
linux-nfs list <linux-nfs@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][Resend] Make NFS-Client readahead tunable
Date: Wed, 17 Sep 2008 13:42:30 +0000 (GMT) [thread overview]
Message-ID: <93909.85868.qm@web26204.mail.ukl.yahoo.com> (raw)
Hi,
...
> Signed-off-by: Martin Knoblauch
>
> diff -urp linux-2.6.27-rc6-git4/fs/nfs/client.c
> linux-2.6.27-rc6-git4-nfs_ra/fs/nfs/client.c
> --- linux-2.6.27-rc6-git4/fs/nfs/client.c 2008-09-17 11:35:21.000000000
> +0200
> +++ linux-2.6.27-rc6-git4-nfs_ra/fs/nfs/client.c 2008-09-17
> 11:55:18.000000000 +0200
> @@ -722,6 +722,11 @@ error:
> }
>
> /*
> + * NFS Client Read-Ahead factor
> +*/
> +unsigned int nfs_ra_factor;
> +
> +/*
> * Load up the server record from information gained in an fsinfo record
> */
> static void nfs_server_set_fsinfo(struct nfs_server *server, struct nfs_fsinfo
> *fsinfo)
> @@ -746,7 +751,11 @@ static void nfs_server_set_fsinfo(struct
> server->rsize = NFS_MAX_FILE_IO_SIZE;
> server->rpages = (server->rsize + PAGE_CACHE_SIZE - 1) >>
> PAGE_CACHE_SHIFT;
>
> - server->backing_dev_info.ra_pages = server->rpages * NFS_MAX_READAHEAD;
> + dprintk("nfs_server_set_fsinfo: rsize, wsize, rpages, \
> + nfs_ra_factor, ra_pages: %d %d %d %d %d\n",
> + server->rsize,server->wsize,server->rpages,
> + nfs_ra_factor,server->rpages * nfs_ra_factor);
> + server->backing_dev_info.ra_pages = server->rpages * nfs_ra_factor;
>
> if (server->wsize > max_rpc_payload)
> server->wsize = max_rpc_payload;
> diff -urp linux-2.6.27-rc6-git4/fs/nfs/inode.c
> linux-2.6.27-rc6-git4-nfs_ra/fs/nfs/inode.c
> --- linux-2.6.27-rc6-git4/fs/nfs/inode.c 2008-09-17 11:35:21.000000000
> +0200
> +++ linux-2.6.27-rc6-git4-nfs_ra/fs/nfs/inode.c 2008-09-17 11:45:09.000000000
> +0200
> @@ -53,6 +53,8 @@
>
> /* Default is to see 64-bit inode numbers */
> static int enable_ino64 = NFS_64_BIT_INODE_NUMBERS_ENABLED;
> +static unsigned int ra_factor __read_mostly = NFS_MAX_READAHEAD;
> +
>
> static void nfs_invalidate_inode(struct inode *);
> static int nfs_update_inode(struct inode *, struct nfs_fattr *);
> @@ -1347,6 +1349,12 @@ static int __init init_nfs_fs(void)
> #endif
> if ((err = register_nfs_fs()) != 0)
> goto out;
> +
> + if (ra_factor < 1 || ra_factor > NFS_MAX_READAHEAD)
> + nfs_ra_factor = NFS_MAX_READAHEAD;
> + else
> + nfs_ra_factor = ra_factor;
> +
So, I think that this is not necessary because it is done ( ... I hope) by the
proc_dointvec_minmax handler. It is correct?
Regards Michael
__________________________________________________
Do You Yahoo!?
Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi
http://mail.yahoo.it
next reply other threads:[~2008-09-17 13:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 13:42 Michael Trimarchi [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-21 12:53 Martin Knoblauch
2008-09-21 12:50 Martin Knoblauch
2008-09-21 13:53 ` Chuck Lever
2008-09-18 11:53 Martin Knoblauch
2008-09-18 18:24 ` Chuck Lever
2008-09-18 19:03 ` Peter Staubach
2008-09-18 9:32 Martin Knoblauch
2008-09-18 8:38 Martin Knoblauch
2008-09-18 8:47 ` Andrew Morton
2008-09-18 8:57 ` Greg Banks
2008-09-18 13:20 ` Peter Zijlstra
2008-09-18 8:19 Martin Knoblauch
2008-09-18 8:45 ` Greg Banks
2008-09-18 7:42 Martin Knoblauch
2008-09-18 8:18 ` Andrew Morton
2008-09-17 17:01 Martin Knoblauch
2008-09-17 16:23 Martin Knoblauch
2008-09-17 16:43 ` Chuck Lever
2008-09-17 16:15 Martin Knoblauch
2008-09-17 16:10 Martin Knoblauch
2008-09-17 16:03 Martin Knoblauch
2008-09-17 13:27 Martin Knoblauch
2008-09-17 13:19 Michael Trimarchi
2008-09-17 13:06 Martin Knoblauch
2008-09-17 14:06 ` Peter Staubach
2008-09-17 15:41 ` Chuck Lever
2008-09-18 1:42 ` Greg Banks
2008-09-18 3:13 ` Andrew Morton
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=93909.85868.qm@web26204.mail.ukl.yahoo.com \
--to=trimarchimichael@yahoo.it \
--cc=knobi@knobisoft.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®