IO-Uring Archive on
 help / color / Atom feed
* [RFC] do_hashed and wq enqueue
@ 2020-02-11 20:20 Pavel Begunkov
  2020-02-11 20:30 ` Jens Axboe
  0 siblings, 1 reply; 3+ messages in thread
From: Pavel Begunkov @ 2020-02-11 20:20 UTC (permalink / raw)
  To: Jens Axboe, io-uring

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-11 20:20 [RFC] do_hashed and wq enqueue Pavel Begunkov
2020-02-11 20:30 ` Jens Axboe
2020-02-11 20:36   ` Pavel Begunkov

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