From: Jens Axboe <axboe@kernel.dk>
To: Mike Christie <michael.christie@oracle.com>,
geert@linux-m68k.org, vverma@digitalocean.com, hdanton@sina.com,
hch@infradead.org, stefanha@redhat.com, jasowang@redhat.com,
mst@redhat.com, sgarzare@redhat.com,
virtualization@lists.linux-foundation.org,
christian.brauner@ubuntu.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 6/9] io_uring: switch to kernel_worker
Date: Mon, 4 Oct 2021 14:30:12 -0600 [thread overview]
Message-ID: <6882df86-9dcd-26ac-af85-9b11d37ba598@kernel.dk> (raw)
In-Reply-To: <20211004192128.381453-7-michael.christie@oracle.com>
On 10/4/21 1:21 PM, Mike Christie wrote:
> Convert io_uring and io-wq to use kernel_worker.
Looks good to me:
Reviewed-by: Jens Axboe <axboe@kernel.dk>
--
Jens Axboe
next prev parent reply other threads:[~2021-10-04 20:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 19:21 [PATCH V3 0/9] Use copy_process/create_io_thread in vhost layer Mike Christie
2021-10-04 19:21 ` [PATCH V3 1/9] fork: Make IO worker options flag based Mike Christie
2021-10-04 19:21 ` [PATCH V3 2/9] fork: pass worker_flags to copy_thread Mike Christie
2021-10-04 19:21 ` [PATCH V3 3/9] fork: move PF_IO_WORKER's kernel frame setup to new flag Mike Christie
2021-10-04 19:21 ` [PATCH V3 4/9] fork: add option to not clone or dup files Mike Christie
2021-10-04 19:21 ` [PATCH V3 5/9] fork: add helper to clone a process Mike Christie
2021-10-04 20:29 ` Jens Axboe
2021-10-05 12:50 ` Christian Brauner
2021-10-05 17:10 ` Mike Christie
2021-10-06 12:12 ` Christian Brauner
2021-10-04 19:21 ` [PATCH V3 6/9] io_uring: switch to kernel_worker Mike Christie
2021-10-04 20:30 ` Jens Axboe [this message]
2021-10-04 19:21 ` [PATCH V3 7/9] fork: Add worker flag to ignore signals Mike Christie
2021-10-04 20:04 ` Jens Axboe
2021-10-05 12:45 ` Christian Brauner
2021-10-04 19:21 ` [PATCH V3 8/9] vhost: move worker thread fields to new struct Mike Christie
2021-10-04 19:21 ` [PATCH V3 9/9] vhost: use kernel_worker to check RLIMITs and inherit v2 cgroups Mike Christie
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=6882df86-9dcd-26ac-af85-9b11d37ba598@kernel.dk \
--to=axboe@kernel.dk \
--cc=christian.brauner@ubuntu.com \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=hdanton@sina.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.christie@oracle.com \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=vverma@digitalocean.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox