From: Chuck Lever <chuck.lever@oracle.com>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH 00/17] RFC: proposed changes to the NFS mount command
Date: Mon, 16 Jul 2007 11:03:43 -0400 [thread overview]
Message-ID: <469B88CF.8040009@oracle.com> (raw)
In-Reply-To: <18074.61070.150991.554588@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]
Neil Brown wrote:
> On Sunday July 15, chuck.lever@oracle.com wrote:
>> Hi Neil-
>>
>> I've got a series of patches to the NFS mount command that prepare it
>> for using a C string to pass mount options to the kernel, rather than
>> a binary nfs_mount_data structure.
>
> I've wondered why that was happening... Can't we just make a version
> x+1 with a big string buffer so new options get put there is regular
> string format and old options stay the way they are?
>
> But I guess that - long term - it is better to be just like other
> filesystems.
>
>
>> The goal of these clean-ups is to allow the creation of a ./configure
>> option that will disable building nfsmount.c and nfs4mount.c, and
>> enable building a version of these files that will introduce support
>> for passing mount options as a string (that work is yet to be done).
>
> Does this mean that you cannot compile nfs-utils to support both old
> and new kernels? Is that really a good plan?
> What is the over-all migration strategy?
The NFS client string mount option support is destined for 2.6.23.
My plan was to build for either binary mount options or string mount
options, switched via a ./configure option. But it's a good point that
currently, the mount command will support all versions of
nfs_mount_data, so it should probably support binary and string options
simultaneously too.
I will reconsider my design. Thanks for the useful feedback.
>> They certainly need some testing yet, but can you take a look at these
>> and tell me if they are generally acceptable or if I need to take a
>> different direction? Hopefully they are straightforward and won't take
>> much of your time.
>
> Some of these are obviously good cleanups. Would it inconvenience you
> if I just picked off the ones I like for now and leave you to rebase?
I would like to do some testing, and maybe some review from others on
the list (hint hint cough). Can you let me know (offline) which ones
you want to take, and I will test those first?
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-07-16 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 3:14 [PATCH 00/17] RFC: proposed changes to the NFS mount command Chuck Lever
2007-07-16 4:05 ` Neil Brown
2007-07-16 8:07 ` Christoph Hellwig
2007-07-16 15:07 ` Chuck Lever
2007-07-16 15:03 ` Chuck Lever [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=469B88CF.8040009@oracle.com \
--to=chuck.lever@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.