From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
Xiaoguang Wang <xiaoguang.wang@linux.alibaba.com>
Cc: Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH 0/4] remove work.func
Date: Mon, 8 Jun 2020 21:14:01 +0300 [thread overview]
Message-ID: <18e05c85-a626-82a9-b60e-d24d1c40682e@gmail.com> (raw)
In-Reply-To: <cover.1591637070.git.asml.silence@gmail.com>
On 08/06/2020 21:08, Pavel Begunkov wrote:
> As discussed, removing ->func from io_wq_work and moving
> it into io-wq.
Xiaoguang Wang, until Jens goes back and picks this up, I'll
also keep the patchset in my github [1]. Just in case you'd
want to play with it.
https://github.com/isilence/linux/commits/rem_work_func
>
> Pavel Begunkov (4):
> io_uring: don't derive close state from ->func
> io_uring: remove custom ->func handlers
> io_uring: don't arm a timeout through work.func
> io_wq: add per-wq work handler instead of per work
>
> fs/io-wq.c | 10 ++-
> fs/io-wq.h | 7 +-
> fs/io_uring.c | 221 +++++++++++++++-----------------------------------
> 3 files changed, 74 insertions(+), 164 deletions(-)
>
--
Pavel Begunkov
next prev parent reply other threads:[~2020-06-08 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 18:08 [PATCH 0/4] remove work.func Pavel Begunkov
2020-06-08 18:08 ` [PATCH 1/4] io_uring: don't derive close state from ->func Pavel Begunkov
2020-06-08 18:08 ` [PATCH 2/4] io_uring: remove custom ->func handlers Pavel Begunkov
2020-06-08 18:08 ` [PATCH 3/4] io_uring: don't arm a timeout through work.func Pavel Begunkov
2020-06-08 18:08 ` [PATCH 4/4] io_wq: add per-wq work handler instead of per work Pavel Begunkov
2020-06-08 18:14 ` Pavel Begunkov [this message]
2020-06-08 20:00 ` [PATCH 0/4] remove work.func Jens Axboe
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=18e05c85-a626-82a9-b60e-d24d1c40682e@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiaoguang.wang@linux.alibaba.com \
/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.