From: Benny Halevy <bhalevy@panasas.com>
To: chao liu <lcnrchpc@gmail.com>
Cc: bwickman@citi.umich.edu, linux-nfs@vger.kernel.org
Subject: Re: some questions about NFSv4.1_Directory_Delegation
Date: Wed, 11 May 2011 13:21:10 -0400 [thread overview]
Message-ID: <4DCAC586.2040205@panasas.com> (raw)
In-Reply-To: <BANLkTik8xfnPCc+z_S_jBU5o6mOYUkOrrQ@mail.gmail.com>
On 2011-05-11 05:30, chao liu wrote:
> *hi everyone,*
> * **Benny and **bwickman**,*
> * i have read the
> article https://wiki.linux-nfs.org/wiki/index.php/CITI_Experience_with_Directory_Delegations
> carefully,*
> * and i checked the latest source code in git hub, i can't
> find the code about directory delegation , so i got two questions to ask,. *ny
> *
> *
> * To Benny, thank you very much, do you think that what are
> the most difficulties or problems to implement Directory_Delegation in
> pnfs?*
Directory delegations are not related to pNFS but rather to NFSv4.1.
I wasn't involved in their experimental implementation in CITI so I
don't know exactly what were their challenges. I can only guess that
the harder parts were dealing with the name cache rather than
implementing the related NFSv4.1 code.
As far as I know, the benefits demonstrated so far are not good enough
to justify the added complexity.
Benny
> *
> *
> * To the author who wrote the article(the author may know
> bwickman), also thanks very much, you said that you have implemented *
> * Directory_Delegation prototype, how can i find the sourcecode? *
> * *
> *
> *
>
>
>
parent reply other threads:[~2011-05-11 15:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <BANLkTik8xfnPCc+z_S_jBU5o6mOYUkOrrQ@mail.gmail.com>]
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=4DCAC586.2040205@panasas.com \
--to=bhalevy@panasas.com \
--cc=bwickman@citi.umich.edu \
--cc=lcnrchpc@gmail.com \
--cc=linux-nfs@vger.kernel.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).