From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring <io-uring@vger.kernel.org>
Subject: [RFC] do_hashed and wq enqueue
Date: Tue, 11 Feb 2020 23:20:04 +0300 [thread overview]
Message-ID: <f0662f54-3964-9cef-151d-3102c9280757@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 476 bytes --]
Hi,
I've been looking for hashed io-wq enqueuing, but not fully understand the
issue. As I remember, it was something about getting around blocking for
buffered I/O. Is that so? Is there any write-up of a thread for this issue?
My case is 2-fd request, and I'm not sure how it should look. For splice() it's
probably Ok to hash the non-pipe end (if any), but I wonder how it should work,
if, for example, the restriction will be removed.
--
Pavel Begunkov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-02-11 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 20:20 Pavel Begunkov [this message]
2020-02-11 20:30 ` [RFC] do_hashed and wq enqueue Jens Axboe
2020-02-11 20:36 ` Pavel Begunkov
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=f0662f54-3964-9cef-151d-3102c9280757@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@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 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).