From: Dave Chinner <david@fromorbit.com>
To: Milosz Tanski <milosz@adfin.com>
Cc: linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-aio@kvack.org,
Mel Gorman <mgorman@suse.de>,
Volker Lendecke <Volker.Lendecke@sernet.de>,
Tejun Heo <tj@kernel.org>, Jeff Moyer <jmoyer@redhat.com>,
Theodore Ts'o <tytso@mit.edu>, Al Viro <viro@zeniv.linux.org.uk>,
linux-api@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH v6 0/7] vfs: Non-blockling buffered fs read (page cache only)
Date: Tue, 11 Nov 2014 17:44:17 +1100 [thread overview]
Message-ID: <20141111064417.GT23575@dastard> (raw)
In-Reply-To: <cover.1415636409.git.milosz@adfin.com>
On Mon, Nov 10, 2014 at 11:40:23AM -0500, Milosz Tanski wrote:
> This patcheset introduces an ability to perform a non-blocking read from
> regular files in buffered IO mode. This works by only for those filesystems
> that have data in the page cache.
>
> It does this by introducing new syscalls new syscalls preadv2/pwritev2. These
> new syscalls behave like the network sendmsg, recvmsg syscalls that accept an
> extra flag argument (RWF_NONBLOCK).
>
> It's a very common patern today (samba, libuv, etc..) use a large threadpool to
> perform buffered IO operations. They submit the work form another thread
> that performs network IO and epoll or other threads that perform CPU work. This
> leads to increased latency for processing, esp. in the case of data that's
> already cached in the page cache.
>
> With the new interface the applications will now be able to fetch the data in
> their network / cpu bound thread(s) and only defer to a threadpool if it's not
> there. In our own application (VLDB) we've observed a decrease in latency for
> "fast" request by avoiding unnecessary queuing and having to swap out current
> tasks in IO bound work threads.
Can you write a test (or set of) for fstests that exercises this new
functionality? I'm not worried about performance, just
correctness....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Milosz Tanski <milosz@adfin.com>
Cc: linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-aio@kvack.org,
Mel Gorman <mgorman@suse.de>,
Volker Lendecke <Volker.Lendecke@sernet.de>,
Tejun Heo <tj@kernel.org>, Jeff Moyer <jmoyer@redhat.com>,
Theodore Ts'o <tytso@mit.edu>, Al Viro <viro@zeniv.linux.org.uk>,
linux-api@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH v6 0/7] vfs: Non-blockling buffered fs read (page cache only)
Date: Tue, 11 Nov 2014 17:44:17 +1100 [thread overview]
Message-ID: <20141111064417.GT23575@dastard> (raw)
Message-ID: <20141111064417.2f0LpvkG33aOaV7fnV0K4N52-lXvGYGob_kTNbLDGLU@z> (raw)
In-Reply-To: <cover.1415636409.git.milosz@adfin.com>
On Mon, Nov 10, 2014 at 11:40:23AM -0500, Milosz Tanski wrote:
> This patcheset introduces an ability to perform a non-blocking read from
> regular files in buffered IO mode. This works by only for those filesystems
> that have data in the page cache.
>
> It does this by introducing new syscalls new syscalls preadv2/pwritev2. These
> new syscalls behave like the network sendmsg, recvmsg syscalls that accept an
> extra flag argument (RWF_NONBLOCK).
>
> It's a very common patern today (samba, libuv, etc..) use a large threadpool to
> perform buffered IO operations. They submit the work form another thread
> that performs network IO and epoll or other threads that perform CPU work. This
> leads to increased latency for processing, esp. in the case of data that's
> already cached in the page cache.
>
> With the new interface the applications will now be able to fetch the data in
> their network / cpu bound thread(s) and only defer to a threadpool if it's not
> there. In our own application (VLDB) we've observed a decrease in latency for
> "fast" request by avoiding unnecessary queuing and having to swap out current
> tasks in IO bound work threads.
Can you write a test (or set of) for fstests that exercises this new
functionality? I'm not worried about performance, just
correctness....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-11-11 6:44 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 16:40 [PATCH v6 0/7] vfs: Non-blockling buffered fs read (page cache only) Milosz Tanski
2014-11-10 16:40 ` Milosz Tanski
2014-11-10 16:40 ` [PATCH v6 1/7] vfs: Prepare for adding a new preadv/pwritev with user flags Milosz Tanski
2014-11-10 16:40 ` Milosz Tanski
2014-11-10 16:40 ` [PATCH v6 2/7] vfs: Define new syscalls preadv2,pwritev2 Milosz Tanski
2014-11-10 16:40 ` Milosz Tanski
2014-11-10 16:40 ` Milosz Tanski
2014-11-11 21:09 ` Jeff Moyer
2014-11-11 21:09 ` Jeff Moyer
2014-11-11 21:09 ` Jeff Moyer
2014-11-12 13:18 ` mohanty bhagaban
2014-11-10 16:40 ` [PATCH v6 3/7] x86: wire up preadv2 and pwritev2 Milosz Tanski
2014-11-10 16:40 ` Milosz Tanski
2014-11-10 16:40 ` [PATCH v6 4/7] vfs: RWF_NONBLOCK flag for preadv2 Milosz Tanski
2014-11-10 16:40 ` [Ocfs2-devel] " Milosz Tanski
2014-11-10 16:40 ` Milosz Tanski
2014-11-10 16:40 ` [PATCH v6 5/7] xfs: add RWF_NONBLOCK support Milosz Tanski
2014-11-10 16:40 ` Milosz Tanski
2014-11-10 16:40 ` [Cluster-devel] [PATCH v6 6/7] fs: pass iocb to generic_write_sync Milosz Tanski
2014-11-10 16:40 ` Milosz Tanski
2014-11-10 16:40 ` Milosz Tanski
2014-11-10 16:40 ` [PATCH v6 7/7] fs: add a flag for per-operation O_DSYNC semantics Milosz Tanski
2014-11-10 16:40 ` Milosz Tanski
2014-11-10 16:40 ` [Ocfs2-devel] " Milosz Tanski
2014-11-10 16:40 ` Milosz Tanski
2014-11-11 6:44 ` Dave Chinner [this message]
2014-11-11 6:44 ` [PATCH v6 0/7] vfs: Non-blockling buffered fs read (page cache only) Dave Chinner
2014-11-11 16:02 ` Milosz Tanski
2014-11-11 16:02 ` Milosz Tanski
2014-11-11 17:03 ` Jeff Moyer
2014-11-11 17:03 ` Jeff Moyer
2014-11-11 17:03 ` Jeff Moyer
2014-11-11 17:03 ` Jeff Moyer
2014-11-11 21:42 ` Dave Chinner
2014-11-11 21:42 ` Dave Chinner
2014-11-11 23:21 ` Jeff Moyer
2014-11-11 23:21 ` Jeff Moyer
2014-11-11 23:21 ` Jeff Moyer
2014-11-11 23:21 ` Jeff Moyer
2014-11-11 22:49 ` Theodore Ts'o
2014-11-11 22:49 ` Theodore Ts'o
2014-11-11 23:27 ` Thomas Gleixner
2014-11-11 23:27 ` Thomas Gleixner
2014-11-11 21:40 ` Dave Chinner
2014-11-11 21:40 ` Dave Chinner
2014-11-14 16:32 ` Jeff Moyer
2014-11-14 16:32 ` Jeff Moyer
2014-11-14 16:39 ` Dave Jones
2014-11-14 16:39 ` Dave Jones
2014-11-14 16:51 ` Jeff Moyer
2014-11-14 16:51 ` Jeff Moyer
2014-11-14 18:46 ` Milosz Tanski
2014-11-14 18:46 ` Milosz Tanski
[not found] ` <20141114163912.GA23769-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-11-14 18:45 ` Milosz Tanski
2014-11-14 18:45 ` Milosz Tanski
2014-11-14 18:52 ` Jeff Moyer
2014-11-14 18:52 ` Jeff Moyer
2014-11-14 18:52 ` Jeff Moyer
2014-11-14 18:52 ` Jeff Moyer
[not found] ` <cover.1415636409.git.milosz-B5zB6C1i6pkAvxtiuMwx3w@public.gmane.org>
2014-11-24 9:53 ` Christoph Hellwig
2014-11-24 9:53 ` Christoph Hellwig
2014-11-25 23:01 ` Andrew Morton
2014-12-02 22:17 ` Milosz Tanski
2014-12-02 22:17 ` Milosz Tanski
2014-12-02 22:42 ` Andrew Morton
2014-12-02 22:42 ` Andrew Morton
2014-12-03 9:10 ` Volker Lendecke
2014-12-03 9:10 ` Volker Lendecke
2014-12-03 16:48 ` Milosz Tanski
[not found] ` <CANP1eJGVyBOt1rQ8jA4tMrNGX5X61-UWbVy6kKj_ByeTqAEOBQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-04 23:11 ` Andrew Morton
2014-12-04 23:11 ` Andrew Morton
2014-12-05 8:17 ` Volker Lendecke
2014-12-05 8:17 ` Volker Lendecke
2015-01-21 14:55 ` Milosz Tanski
2015-01-21 14:55 ` Milosz Tanski
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=20141111064417.GT23575@dastard \
--to=david@fromorbit.com \
--cc=Volker.Lendecke@sernet.de \
--cc=hch@infradead.org \
--cc=jmoyer@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=milosz@adfin.com \
--cc=mtk.manpages@gmail.com \
--cc=tj@kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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.