public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Gabriel Krisman Bertazi <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH 0/2] io-wq: cleanup io_wq and io_wqe
Date: Thu, 23 Mar 2023 13:19:04 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 3/21/23 7:16?PM, Gabriel Krisman Bertazi wrote:
> Hi Jens,
> 
> This tides up the io-wq internal interface by dropping the io_wqe/io_wq
> separation, which no longer makes sense since commit
> 0654b05e7e65 ("io_uring: One wqe per wq").  We currently have a single
> io_wqe instance per io_wq, which is embedded in the structure.  This
> patchset merges the two, dropping bit of code to go from one to the
> other in the io-wq implementation.
> 
> I don't expect it to have any positive impact on performance, of course,
> since hopefully the compiler optimizes it, but still, it is nice clean
> up.  To be sure, I measured with some mmtests microbenchmarks and I haven't
> seen differences with or without the patchset.
> 
> Patch 2 is slightly big to review but the use of wq and wqe is
> intrinsically connected; it was a bit hard to break it in more pieces.
> 
> Tested by running liburing's testsuite and mmtests performance
> microbenchmarks (which uses fio).
> 
> Based on your for-next branch.

Nice! This is a great continuation of getting rid of the per-node worker
setup.

-- 
Jens Axboe


  parent reply	other threads:[~2023-03-23 19:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22  1:16 [PATCH 0/2] io-wq: cleanup io_wq and io_wqe Gabriel Krisman Bertazi
2023-03-22  1:16 ` [PATCH 1/2] io-wq: Move wq accounting to io_wq Gabriel Krisman Bertazi
2023-03-22  1:16 ` [PATCH 2/2] io-wq: Drop struct io_wqe Gabriel Krisman Bertazi
2023-03-23 19:19 ` Jens Axboe [this message]
2023-03-23 19:31 ` [PATCH 0/2] io-wq: cleanup io_wq and io_wqe 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 \
    [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