linux-kernel - is nfsd sync or async?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <AANLkTimvSygr1DqMnc97RVsaXik9s+iFRHUaXrHPyYiQ@mail.gmail.com>
Date:	Mon, 9 Aug 2010 09:02:51 -0400
From:	Yuehai Xu <yuehaixu@...il.com>
To:	linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org
Cc:	yhxu@...ne.edu
Subject: is nfsd sync or async?

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 appreciated!

Yuehai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/