From: Alex Sidorenko <alexandre.sidorenko@hp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: FLushing cached writes in nfs_getattr() and stat() delay
Date: Thu, 6 Nov 2008 14:55:21 -0500 [thread overview]
Message-ID: <200811061455.21831.alexandre.sidorenko@hp.com> (raw)
In-Reply-To: <B01C5173-08DF-4EF9-8186-BEBDA8EE9862@oracle.com>
On November 6, 2008 02:45:34 pm Chuck Lever wrote:
> There's a difference between an asynchronous RPC request, and an
> asynchronous write request.
>
> An async RPC means the process doesn't wait for the request to finish=
,
> it can perform other housekeeping.
>
> An async write means that the client delays sending NFS writes,
> maintaining the dirty data in its memory. =A0It can send the NFS writ=
e
> requests by means of an async RPC if it wishes. =A0A synchronous writ=
e
> means that the client will block the application until the server has
> replied that the dirty data is on the server's disk.
Thank you for clarification. I knew what RPC-async means but for some r=
eason=20
forgot what SYNC-write means, sorry for confusion. And yes, I should ha=
ve=20
looked at /proc/mounts instead of /etc/mtab
Regards,
Alex
--=20
------------------------------------------------------------------
Alexandre Sidorenko email: asid@hp.com
Global Solutions Engineering: Unix Networking
Hewlett-Packard (Canada)
------------------------------------------------------------------
prev parent reply other threads:[~2008-11-06 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 15:34 FLushing cached writes in nfs_getattr() and stat() delay Alex Sidorenko
2008-11-06 16:40 ` Chuck Lever
2008-11-06 18:49 ` Trond Myklebust
[not found] ` <1225997396.387.30.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-11-06 19:15 ` Chuck Lever
2008-11-06 19:22 ` Alex Sidorenko
2008-11-06 19:32 ` Trond Myklebust
2008-11-06 19:45 ` Chuck Lever
2008-11-06 19:55 ` Alex Sidorenko [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=200811061455.21831.alexandre.sidorenko@hp.com \
--to=alexandre.sidorenko@hp.com \
--cc=chuck.lever@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.