From: Yudong Gao <stgyd@umich.edu>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Implementation of delegation
Date: Mon, 12 Jul 2010 15:00:31 -0700 [thread overview]
Message-ID: <AANLkTimjFbkLIs4GIdR_S06bu7PPOV-JUj5uGAMs7IjG@mail.gmail.com> (raw)
In-Reply-To: <1278971292.14605.2.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
Hi Trond,
Thanks for the prompt reply!
I find that in _nfs_do_open(), _nfs4_proc_open(), which do the RPC
call to the remote server, is always called before
nfs4_opendata_to_nfs4_state(), which will further invoke
nfs4_try_open_cached().
Does this means that whenever is file is opened, the client always
need to talk to the server first?
Thanks!
best,
Yudong
On Mon, Jul 12, 2010 at 2:48 PM, Trond Myklebust
<trond.myklebust@fys.uio.no> wrote:
> On Mon, 2010-07-12 at 14:37 -0700, Yudong Gao wrote:
>> Hi,
>>
>> I am reading the NFS source code of the file open function in kernel
>> 2.6.34, but I cannot find any implementation with delegation to allow
>> client to open a file locally without contacting the server. We are
>> tying to use delegation to do something interesting. So I am wondering
>> how much delegation support specified in the NFS 4.1 protocol is
>> available in the current Linux implementation?
>
> What's wrong with nfs4_try_open_cached()? It even works with NFSv4.0...
>
> Trond
>
>
next prev parent reply other threads:[~2010-07-12 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 21:37 Implementation of delegation Yudong Gao
[not found] ` <AANLkTik1dbBEnyqMEw9snDhjglJiDQJKs4dFdenqXaGJ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-12 21:48 ` Trond Myklebust
[not found] ` <1278971292.14605.2.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-07-12 22:00 ` Yudong Gao [this message]
2010-07-12 22:07 ` Trond Myklebust
[not found] ` <1278972475.14605.9.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-07-12 22:19 ` Yudong Gao
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=AANLkTimjFbkLIs4GIdR_S06bu7PPOV-JUj5uGAMs7IjG@mail.gmail.com \
--to=stgyd@umich.edu \
--cc=linux-nfs@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).