From: Valdis.Kletnieks@vt.edu
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Pierre Ossman <drzeus-list@drzeus.cx>,
Peter Staubach <staubach@redhat.com>,
nfsv4@linux-nfs.org, Andrew Morton <akpm@linux-foundation.org>,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [NFS] What's slated for inclusion in 2.6.24-rc1 from the NFS client git tree...
Date: Fri, 05 Oct 2007 13:30:10 -0400 [thread overview]
Message-ID: <30494.1191605410@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 04 Oct 2007 10:00:50 EDT." <1191506450.6685.17.camel@heimdal.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
On Thu, 04 Oct 2007 10:00:50 EDT, Trond Myklebust said:
> How about a boot/module parameter to turn it on or off?
>
> I don't see any point in having a sysctl for something like this: either
> you have legacy applications or you don't. It is not something that you
> switch off as you go off to lunch.
How does Joe Sysadmin tell if he has an affected legacy app or not?
(The obvious "try it and see what breaks" is a non-starter for many places,
because you too easily end up in a loop of "enable it, find 4-5 show stoppers,
turn it off, fix them, lather rinse repease". Been there, done that, got
the tshirt - a project I got dragged into involves a large storage array that
appears to insist on exporting 64-bit stuff, and a large farm of clients that
are very 64-bit unclean....)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-10-05 17:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 23:41 Trond Myklebust
2007-10-03 23:52 ` Jeff Garzik
2007-10-04 6:52 ` Pierre Ossman
2007-10-04 14:00 ` [NFS] " Trond Myklebust
2007-10-04 16:43 ` Pierre Ossman
2007-10-04 18:42 ` Andrew Morton
2007-10-04 19:16 ` Trond Myklebust
2007-10-04 19:41 ` Peter Staubach
2007-10-05 6:25 ` Pierre Ossman
2007-10-05 17:36 ` Trond Myklebust
2007-10-05 17:54 ` Pierre Ossman
2007-10-04 19:59 ` Andrew Morton
2007-10-05 0:58 ` Trond Myklebust
2007-10-05 17:30 ` Valdis.Kletnieks [this message]
2007-10-05 17:52 ` Trond Myklebust
2007-10-05 18:00 ` Jeff Layton
2007-10-08 8:36 ` Greg Banks
2007-10-05 18:12 ` Jeff Layton
2007-10-07 22:56 ` David Chinner
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=30494.1191605410@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.org \
--cc=staubach@redhat.com \
--cc=trond.myklebust@fys.uio.no \
/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®