From: Al Viro <viro@zeniv.linux.org.uk>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Benjamin LaHaise <bcrl@kvack.org>,
linux-fsdevel@vger.kernel.org, linux-aio@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] aio: Support read/write with non-iter file-ops
Date: Fri, 19 Jul 2019 00:17:52 +0100 [thread overview]
Message-ID: <20190718231751.GV17978@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20190718231054.8175-1-bjorn.andersson@linaro.org>
On Thu, Jul 18, 2019 at 04:10:54PM -0700, Bjorn Andersson wrote:
> Implement a wrapper for aio_read()/write() to allow async IO on files
> not implementing the iter version of read/write, such as sysfs. This
> mimics how readv/writev uses non-iter ops in do_loop_readv_writev().
IDGI. How would that IO manage to be async? And what's the point
using aio in such situations in the first place?
next prev parent reply other threads:[~2019-07-18 23:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 23:10 [PATCH] aio: Support read/write with non-iter file-ops Bjorn Andersson
2019-07-18 23:17 ` Al Viro [this message]
2019-07-18 23:43 ` Bjorn Andersson
2019-07-18 23:56 ` Benjamin LaHaise
2019-07-19 0:36 ` Bjorn Andersson
2019-07-19 0:07 ` Al Viro
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=20190718231751.GV17978@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=bcrl@kvack.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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.