From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>,
io-uring <[email protected]>
Subject: Re: [PATCH] io_uring: use task_work for links if possible
Date: Thu, 25 Jun 2020 15:37:27 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
>
On 6/25/20 2:28 PM, Pavel Begunkov wrote:
> On 25/06/2020 21:27, Jens Axboe wrote:
>> Currently links are always done in an async fashion, unless we
>> catch them inline after we successfully complete a request without
>> having to resort to blocking. This isn't necessarily the most efficient
>> approach, it'd be more ideal if we could just use the task_work handling
>> for this.
>
> Well, you beat me on this. As mentioned, I was going to rebase it after
> lending iopoll fixes. Nice numbers! A small comment below, but LGTM.
> I'll review more formally on a fresh head.
I thought you were doing this for the retry -EAGAIN based stuff, didn't
know you had plans on links! If so, I would have left it alone. This was
just a quick idea and execution this morning.
> Could you push it to a branch? My other patches would conflict.
Yep, I'll push it out now.
>> +static void __io_req_task_submit(struct io_kiocb *req)
>> +{
>> + struct io_ring_ctx *ctx = req->ctx;
>> +
>> + __set_current_state(TASK_RUNNING);
>> + if (!io_sq_thread_acquire_mm(ctx, req)) {
>
> My last patch replaced it with "__" version. Is it merge problems
> or intended as this?
I'll make sure it applies on for-5.9/io_uring, and then I'll sort out
any merge issues by pulling in io_uring-5.8 to there, if we need to.
--
Jens Axboe
next prev parent reply other threads:[~2020-06-25 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 18:27 [PATCH] io_uring: use task_work for links if possible Jens Axboe
2020-06-25 20:28 ` Pavel Begunkov
2020-06-25 21:37 ` Jens Axboe [this message]
2020-06-26 9:41 ` Pavel Begunkov
2020-06-26 20:27 ` Pavel Begunkov
2020-06-26 20:43 ` Jens Axboe
2020-06-26 21:20 ` Pavel Begunkov
2020-06-27 1:45 ` Jens Axboe
2020-06-27 10:57 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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