linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Adamson <andros@netapp.com>
To: Yudong Gao <stgyd@umich.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Write delegation
Date: Wed, 4 Aug 2010 16:59:49 -0400	[thread overview]
Message-ID: <97A00951-577C-4365-AA38-3C6E2D03B372@netapp.com> (raw)
In-Reply-To: <AANLkTimr9QfF0+MJ47hUihJgSLVOfquR=Atp4iV5D2gr@mail.gmail.com>


On Aug 4, 2010, at 3:21 PM, Yudong Gao wrote:

> Hi,
> 
> I am not able to find the implementation of directory delegation,
> either. Similarly, the callback functions CB_NOTIFY is not
> implemented, either. I find that in preprocss_nfs41_op() in
> callback_xdr.c, whenever a CB_NOTIFY is encountered, an
> NFS4ERR_NOTSUPP is returned directly.

CB_NOTIFY is not currently supported on the Linux NFS client.

> 
> Am I missing something? Or they are just not supported in the current version?
> 
> Thanks a lot!
> 
> best,
> 
> Yudong
> 
> On Mon, Aug 2, 2010 at 5:17 PM, Yudong Gao <stgyd@umich.edu> wrote:
>> Hi,
>> 
>> I am looking at the delegation implementation in the source code of
>> NFS 4.1 in kernel 2.6.32.15. I can find the code for read delegation,
>> which is working and can serve the read requests locally. But I can
>> never find the code about write delegation, which is supposed to cache
>> the write update locally. I try to look at the functions including
>> nfs_writepage(s), nfs_file_flush() but none of them checks or uses the
>> write delegation.
>> 
>> Is write delegation currently implemented in NFS 4.1?

Write delegation is supported but I don't think write behavior changes - writes are still cached and flushed as without a write delegation. The write delegation does prevent open/close and lock/locku from being put on the wire.

-->Andy

>> 
>> Thanks!
>> 
>> best,
>> 
>> Yudong
>> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2010-08-04 20:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03  0:17 Write delegation Yudong Gao
     [not found] ` <AANLkTi=2KYZ-8qaXMG=C_s617q3k1Ocs7h1gyd8=RpY6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-04 19:21   ` Yudong Gao
2010-08-04 20:59     ` Andy Adamson [this message]
2010-08-04 21:11       ` Yudong Gao
2010-08-04 21:22         ` Trond Myklebust
2010-08-04 21:40           ` Yudong Gao
2010-08-05  0:52             ` Trond Myklebust
2010-08-05  1:22               ` Yudong Gao
     [not found]                 ` <AANLkTinq-q5f5QjCBiXuZMJY6dHajpDPZ7aO55ipNZcE-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-05  1:25                   ` Trond Myklebust
2010-08-05 18:10                     ` Yudong Gao
2010-08-05 20:13                       ` Yudong Gao
2010-08-05 20:38                         ` fscache Gilliam, PaulX J
2010-08-04 21:09     ` Write delegation Trond Myklebust
2010-08-04 21:20       ` Yudong Gao
  -- strict thread matches above, loose matches on Subject: below --
2019-07-23 21:21 Write Delegation Diyu Zhou
2019-07-24 12:03 ` Benjamin Coddington

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=97A00951-577C-4365-AA38-3C6E2D03B372@netapp.com \
    --to=andros@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=stgyd@umich.edu \
    /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).