From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Jamie Lokier <jamie@shareable.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [2/3] POHMELFS: Documentation.
Date: Sat, 14 Jun 2008 23:25:31 +0400 [thread overview]
Message-ID: <20080614192531.GA15221@2ka.mipt.ru> (raw)
In-Reply-To: <1213469136.7149.36.camel@localhost>
On Sat, Jun 14, 2008 at 02:45:36PM -0400, Trond Myklebust (trond.myklebust@fys.uio.no) wrote:
>
> You're confusing write gathering with asynchronous I/O...
>
> NFS attempts to send multiple contiguous pages in one I/O request, and
> so it has a mechanism for collecting them and dispatching the I/O as
> soon as we have enough pages for an RPC call.
>
> The actual RPC call is then handled by the sunrpc layer and is done
> fully asynchronously using non-blocking I/O.
Well, yes, I did not dig into rpc as is deep enough, but checked how
callbacks are prepared in respect to ioflags namely RPC_FLAGS_ASYNC. I
was confused with the fact, that system did not yet process request, but
accounted stats for it, but likely that stats are just intended to
show exactly what was queued for (later) processing.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-06-14 19:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 16:37 [0/3] POHMELFS high performance network filesystem. First steps in parallel processing Evgeniy Polyakov
2008-06-13 16:40 ` [1/3] POHMELFS: VFS trivial change Evgeniy Polyakov
2008-06-13 16:41 ` [2/3] POHMELFS: Documentation Evgeniy Polyakov
2008-06-14 2:15 ` Jamie Lokier
2008-06-14 6:56 ` Evgeniy Polyakov
2008-06-14 9:49 ` Jeff Garzik
2008-06-14 18:45 ` Trond Myklebust
2008-06-14 19:25 ` Evgeniy Polyakov [this message]
2008-06-15 4:27 ` Sage Weil
2008-06-15 5:57 ` Evgeniy Polyakov
2008-06-15 16:41 ` Sage Weil
2008-06-15 17:50 ` Evgeniy Polyakov
2008-06-16 3:17 ` Sage Weil
2008-06-16 10:20 ` Evgeniy Polyakov
2008-06-13 16:42 ` [3/3] POHMELFS high performance network filesystem Evgeniy Polyakov
2008-06-15 7:47 ` Vegard Nossum
2008-06-15 9:14 ` Evgeniy Polyakov
2008-06-14 9:52 ` [0/3] POHMELFS high performance network filesystem. First steps in parallel processing Jeff Garzik
2008-06-14 10:10 ` Evgeniy Polyakov
-- strict thread matches above, loose matches on Subject: below --
2008-07-07 18:07 Evgeniy Polyakov
2008-07-07 18:10 ` [2/3] POHMELFS: Documentation Evgeniy Polyakov
2008-07-12 7:01 ` Pavel Machek
2008-07-12 7:26 ` Evgeniy Polyakov
2008-10-07 21:19 [0/3] The new POHMELFS release Evgeniy Polyakov
2008-10-07 21:21 ` [2/3] POHMELFS: documentation Evgeniy Polyakov
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=20080614192531.GA15221@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 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).