IO-Uring Archive on
 help / color / Atom feed
From: Pavel Begunkov <>
To: Jens Axboe <>, io-uring <>
Subject: [RFC] do_hashed and wq enqueue
Date: Tue, 11 Feb 2020 23:20:04 +0300
Message-ID: <> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 476 bytes --]


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 --]

             reply index

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 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

IO-Uring Archive on

Archives are clonable:
	git clone --mirror io-uring/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 io-uring io-uring/ \
	public-inbox-index io-uring

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone