From: Olaf Kirch <okir@suse.de>
To: Neil Brown <neilb@suse.de>
Cc: Chuck Lever <chucklever@gmail.com>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>,
Greg Banks <gnb@melbourne.sgi.com>
Subject: Re: [PATCH 3/4] Add /proc/sys/fs/nfs sysctls to nfsd module
Date: Sat, 5 Aug 2006 15:15:16 +0200 [thread overview]
Message-ID: <20060805131516.GA9703@suse.de> (raw)
In-Reply-To: <17619.55834.927259.225840@cse.unsw.edu.au>
On Sat, Aug 05, 2006 at 09:36:58AM +1000, Neil Brown wrote:
> So of the three options - the one that I find it hardest to justify
> if /proc/sys, which is what the original patch uses - sad.
I have no problem with fixing up the patch to use any other mechanism.
But if we do this, I think we should move all tunables. Having them
in multiple places just sucks. This includes /proc/sys/sunrpc/*_debug
(which ended up in /proc/sys/sunrpc because a the time I wrote this code,
there was no way a module could create a sysctl directory).
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
okir@suse.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2006-08-05 13:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 11:05 [PATCH 3/4] Add /proc/sys/fs/nfs sysctls to nfsd module Olaf Kirch
2006-08-03 16:52 ` Chuck Lever
2006-08-03 17:08 ` Trond Myklebust
2006-08-04 17:55 ` Olaf Kirch
2006-08-04 8:43 ` Greg Banks
2006-08-04 15:36 ` Trond Myklebust
2006-08-04 17:52 ` Olaf Kirch
2006-08-04 18:23 ` Trond Myklebust
2006-08-04 19:16 ` Peter Staubach
2006-08-04 20:06 ` Olaf Kirch
2006-08-07 4:02 ` Trond Myklebust
2006-08-04 23:36 ` Neil Brown
2006-08-05 13:15 ` Olaf Kirch [this message]
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=20060805131516.GA9703@suse.de \
--to=okir@suse.de \
--cc=chucklever@gmail.com \
--cc=gnb@melbourne.sgi.com \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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