From: Yuehai Xu <yuehaixu@gmail.com>
To: linux-nfs@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, green.trace@gmail.com,
yuehai.xu@gmail.com,
yhxu-jgEIgUtgKzeHXe+LvDLADg@public.gmane.org
Subject: Re: is nfsd sync or async?
Date: Mon, 9 Aug 2010 22:44:35 -0400 [thread overview]
Message-ID: <AANLkTimaOiC4eo3Zqn-wO62sV9hVMsNeF-vqkMGi6kVR@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimU8OCKCaj0b5Ueg__c5DKSKGJWxoZUNK5xeyHk-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, Aug 9, 2010 at 8:00 AM, Yuehai Xu <yuehaixu@gmail.com> wrote:
> Hi all,
>
> Suppose there is only one nfsd and two clients are sending random read
> requests to this daemon. In this way, read ahead of the client should
> not work since the requests are random. The requests between these two
> clients should be async, while the requests from any one client of the
> two should be sync. My question is about how will the nfsd handle
> these requests, using sync or async mode in the kernel? Say, will nfsd
> never handle the next request unless the previous request has been
> served, without considering which clients the request belongs to? Or
> nfsd just dispatch async requests to the lower level as soon as it
> receives a request?
>
> Any answer will be appreciate!
>
> Yuehai
>
I review the code of NFS and notice that the read operation of NFS
will invoke generic_file_aio_read(), which means the requests(from the
case I mentioned above) dispatched by a nfsd should be sync to each
other, is that correct?
Thanks,
Yuehai
next prev parent reply other threads:[~2010-08-10 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 12:00 is nfsd sync or async? Yuehai Xu
[not found] ` <AANLkTimU8OCKCaj0b5Ueg__c5DKSKGJWxoZUNK5xeyHk-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-10 2:44 ` Yuehai Xu [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-09 13:02 Yuehai Xu
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=AANLkTimaOiC4eo3Zqn-wO62sV9hVMsNeF-vqkMGi6kVR@mail.gmail.com \
--to=yuehaixu@gmail.com \
--cc=green.trace@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=yhxu-jgEIgUtgKzeHXe+LvDLADg@public.gmane.org \
--cc=yuehai.xu@gmail.com \
/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).