From: "H. Peter Anvin" <hpa@zytor.com>
To: maximilian attems <max-U9r9yeDMy7A@public.gmane.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
linux-nfs@vger.kernel.org, klibc@zytor.com,
Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: [klibc] nfs MNT include cleanup
Date: Tue, 18 Aug 2009 09:04:45 -0700 [thread overview]
Message-ID: <4A8AD11D.4000809@zytor.com> (raw)
In-Reply-To: <20090818124406.GD13440-P4at2qFsAtP5lb2fJPEjcQ@public.gmane.org>
On 08/18/2009 05:44 AM, maximilian attems wrote:
> On Tue, Aug 18, 2009 at 08:45:49AM -0400, Chuck Lever wrote:
>> However, the kernel has its own NFS mount client (the piece that
>> handles rpcbind query and obtaining the root file handle), and you can
>> pass a C string of mount options to the kernel with mount(2). Perhaps
>> in the long term, you might consider replacing the specialized code in
>> klibc with simply passing the server, export path, and mount options
>> right to the kernel and let it do the work. This should work with any
>> kernel later than 2.6.23.
>>
>> I'm happy to help with any questions.
>
> sounds good indeed.
> a quick one: can it do nfs v4 mounts?
>
I believe that was the reason for the change in the first place, and
yes, klibc should *absolutely* use it.
-hpa (who once again apologizes for lack of time...)
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
prev parent reply other threads:[~2009-08-18 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 10:44 nfs MNT include cleanup maximilian attems
[not found] ` <20090811104418.GA6175-U9r9yeDMy7A@public.gmane.org>
2009-08-11 18:55 ` Chuck Lever
2009-08-18 10:36 ` maximilian attems
[not found] ` <20090818103653.GB3954-U9r9yeDMy7A@public.gmane.org>
2009-08-18 12:45 ` Chuck Lever
2009-08-18 12:44 ` maximilian attems
[not found] ` <20090818124406.GD13440-P4at2qFsAtP5lb2fJPEjcQ@public.gmane.org>
2009-08-18 13:19 ` Chuck Lever
2009-08-18 16:04 ` H. Peter Anvin [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=4A8AD11D.4000809@zytor.com \
--to=hpa@zytor.com \
--cc=Trond.Myklebust@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=klibc@zytor.com \
--cc=linux-nfs@vger.kernel.org \
--cc=max-U9r9yeDMy7A@public.gmane.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).