From: Wu Fengguang <fengguang.wu@intel.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFS commit: sync or async?
Date: Fri, 23 Jul 2010 08:47:56 +0800 [thread overview]
Message-ID: <20100723004756.GB5246@localhost> (raw)
In-Reply-To: <1279802335.3621.8.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
> Hi Fengguang,
>
> Are you sure this trace is from a recent kernel? In all kernels prior to
> 2.6.34-rc3, COMMIT was a synchronous RPC call, which would explain the
> above trace.
My god. I was running 2.6.34-rc1 and reading 2.6.35-rc4 code ..
Sorry for the noise!
Thanks,
Fengguang
prev parent reply other threads:[~2010-07-23 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 7:36 NFS commit: sync or async? Wu Fengguang
2010-07-22 12:38 ` Trond Myklebust
[not found] ` <1279802335.3621.8.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-07-23 0:47 ` Wu Fengguang [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=20100723004756.GB5246@localhost \
--to=fengguang.wu@intel.com \
--cc=Trond.Myklebust@netapp.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