From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>,
[email protected], [email protected]
Subject: Re: [PATCH 0/2] io-wq sharing
Date: Tue, 28 Jan 2020 03:08:59 +0300 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
[-- Attachment #1.1: Type: text/plain, Size: 923 bytes --]
On 28/01/2020 03:06, Pavel Begunkov wrote:
> rip-off of Jens io-wq sharing patches allowing multiple io_uring
> instances to be bound to a single io-wq. The differences are:
> - io-wq, which we would like to be shared, is passed as io_uring fd
> - fail, if can't share. IMHO, it's always better to fail fast and loud
>
> I didn't tested it after rebasing, but hopefully won't be a problem.
>
Ahh, wrong version. Sorry for that
> p.s. on top of ("io_uring/io-wq: don't use static creds/mm assignments")
>
> Pavel Begunkov (2):
> io-wq: allow grabbing existing io-wq
> io_uring: add io-wq workqueue sharing
>
> fs/io-wq.c | 10 ++++++
> fs/io-wq.h | 1 +
> fs/io_uring.c | 67 +++++++++++++++++++++++++++--------
> include/uapi/linux/io_uring.h | 4 ++-
> 4 files changed, 67 insertions(+), 15 deletions(-)
>
--
Pavel Begunkov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-01-28 0:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 0:06 [PATCH 0/2] io-wq sharing Pavel Begunkov
2020-01-28 0:06 ` [PATCH 1/2] io-wq: allow grabbing existing io-wq Pavel Begunkov
2020-01-28 0:06 ` [PATCH 2/2] io_uring: add io-wq workqueue sharing Pavel Begunkov
2020-01-28 0:08 ` Pavel Begunkov [this message]
2020-01-28 0:15 ` [PATCH v2 0/2] io-wq sharing Pavel Begunkov
2020-01-28 0:15 ` [PATCH v2 1/2] io-wq: allow grabbing existing io-wq Pavel Begunkov
2020-01-28 0:18 ` Pavel Begunkov
2020-01-28 0:20 ` Jens Axboe
2020-01-28 0:15 ` [PATCH v2 2/2] io_uring: add io-wq workqueue sharing Pavel Begunkov
2020-01-28 0:22 ` Jens Axboe
2020-01-28 0:29 ` [PATCH v2 0/2] io-wq sharing Jens Axboe
2020-01-28 7:41 ` 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] \
[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