linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:19:26 -0700	[thread overview]
Message-ID: <AANLkTilKhiHmLdssHLhW4_0bzb15cJnvlAMhjC5akPVi@mail.gmail.com> (raw)
In-Reply-To: <1278972475.14605.9.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>

I see! Thanks a lot for the pointer!

best,

Yudong

On Mon, Jul 12, 2010 at 3:07 PM, Trond Myklebust
<trond.myklebust@fys.uio.no> wrote:
> On Mon, 2010-07-12 at 15:00 -0700, Yudong Gao wrote:
>> 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?
>
> The actual RPC call is skipped if the call to can_open_cached() succeeds
> in nfs4_open_prepare(). In that case, we just grab the sequence, which
> ensures that we remain serialised w.r.t. CLOSE and OPEN_DOWNGRADE calls.
>
> Trond
>
>

      parent reply	other threads:[~2010-07-12 22:19 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
2010-07-12 22:07         ` Trond Myklebust
     [not found]           ` <1278972475.14605.9.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-07-12 22:19             ` Yudong Gao [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=AANLkTilKhiHmLdssHLhW4_0bzb15cJnvlAMhjC5akPVi@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).