From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Yudong Gao <stgyd@umich.edu>
Cc: Andy Adamson <andros@netapp.com>, linux-nfs@vger.kernel.org
Subject: Re: Write delegation
Date: Wed, 04 Aug 2010 21:25:21 -0400 [thread overview]
Message-ID: <1280971521.2865.30.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <AANLkTinq-q5f5QjCBiXuZMJY6dHajpDPZ7aO55ipNZcE-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, 2010-08-04 at 18:22 -0700, Yudong Gao wrote:
> But for the integration with NFS, it is confusing. The
> fscache_write_page() is called only in one place:
> nfs_readpage_release(). So a NFS page is only written to fscache after
> it is read from the server in nfs_readpage. So my question is, if a
> page is locally modified, when its data is propagated to fscache? I
> check the nfs_write_begin() and nfs_write_end() but cannot find any
> relative implementation.
See my previous answer. fscache only supports read-only files in NFS.
Trond
next prev parent reply other threads:[~2010-08-05 1:25 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
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 [this message]
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=1280971521.2865.30.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=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).