[PATCHSET,0/2] tw/wakeup tweaks

Message ID	20221217204840.45213-1-axboe@kernel.dk (mailing list archive)
Headers	show Return-Path: <io-uring-owner@kernel.org> From: Jens Axboe <axboe@kernel.dk> To: io-uring@vger.kernel.org Cc: dylany@meta.com, asml.silence@gmail.com Subject: [PATCHSET 0/2] tw/wakeup tweaks Date: Sat, 17 Dec 2022 13:48:38 -0700 Message-Id: <20221217204840.45213-1-axboe@kernel.dk> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk
Series	tw/wakeup tweaks \| expand [PATCHSET,0/2] tw/wakeup tweaks [1/2] io_uring: don't use TIF_NOTIFY_SIGNAL to test for availability of task_work [2/2] io_uring: include task_work run after scheduling in wait for events

Message ID

20221217204840.45213-1-axboe@kernel.dk (mailing list archive)

Headers

From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Cc: dylany@meta.com, asml.silence@gmail.com
Subject: [PATCHSET 0/2] tw/wakeup tweaks
Date: Sat, 17 Dec 2022 13:48:38 -0700
Message-Id: <20221217204840.45213-1-axboe@kernel.dk>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Series

tw/wakeup tweaks | expand

Message

Jens Axboe Dec. 17, 2022, 8:48 p.m. UTC

Hi,

One patch tweaks when we think we have task_work pending to be more
inclusive rather than gate on TIF_NOTIFY_SIGNAL, patch two ensures we
don't do extra loops io_cqring_wait() - and just as importantly, that
the expected run path for task_work will not have the task itself
adding to the ctx->cq_wait waitqueue.