public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Stefan Hajnoczi <[email protected]>, Ming Lei <[email protected]>
Cc: [email protected]
Subject: Re: Resizing io_uring SQ/CQ?
Date: Wed, 15 Mar 2023 09:18:22 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <20230310165628.GA491749@fedora>

On 3/10/23 9:56 AM, Stefan Hajnoczi wrote:
> On Fri, Mar 10, 2023 at 11:14:04PM +0800, Ming Lei wrote:
> 
> Hi Ming,
> Another question about this:
> 
> Does the io worker thread pool have limits so that eventually work
> queues up and new work is not able to execute until in-flight work
> completes?

It's effectively limited by how many processes you are allowed to
create. If you exceed that limit, then yes you would have work
sitting behind other work, and that new work won't get to run
before _something_ completes.

But no ring sizing will save that, you've effectively exhausted
any resources in the system, at least for you.

-- 
Jens Axboe



  reply	other threads:[~2023-03-15 15:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 13:48 Resizing io_uring SQ/CQ? Stefan Hajnoczi
2023-03-10  1:38 ` Ming Lei
2023-03-10  2:58   ` Jens Axboe
2023-03-10  3:42     ` Vito Caputo
2023-03-10 13:44     ` Stefan Hajnoczi
2023-03-10 15:14       ` Ming Lei
2023-03-10 16:39         ` Stefan Hajnoczi
2023-03-10 16:56         ` Stefan Hajnoczi
2023-03-15 15:18           ` Jens Axboe [this message]
2023-03-15 15:15         ` Stefan Hajnoczi
2023-03-15 15:19           ` Jens Axboe
2023-03-15 19:01             ` Stefan Hajnoczi
2023-03-15 19:10               ` 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] \
    [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