From: Jens Axboe <[email protected]>
To: Stefan Hajnoczi <[email protected]>
Cc: Ming Lei <[email protected]>, [email protected]
Subject: Re: Resizing io_uring SQ/CQ?
Date: Wed, 15 Mar 2023 13:10:26 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <20230315190147.GA7517@fedora>
On 3/15/23 1:01?PM, Stefan Hajnoczi wrote:
> On Wed, Mar 15, 2023 at 09:19:39AM -0600, Jens Axboe wrote:
>> On 3/15/23 9:15?AM, Stefan Hajnoczi wrote:
>>> Hi Ming and Jens,
>>> It would be great if you have time to clarify whether deadlocks can
>>> occur or not. If you have any questions about the scenario I was
>>> describing, please let me know.
>>
>> I don't believe there is. In anything not ancient, you are always
>> allowed to submit and the documentation should be updated to
>> describe that correctly. We don't return -EBUSY for submits with
>> overflow pending.
>
> Thank you both for the discussion! It has helped.
Would like to add that while I don't think ring resizing is necessary
because of any potential deadlocks, I do think CQ ring resizing would be
a useful addition to avoid networked applications using giant CQ ring
sizes by default... If we had that, you could start smaller and make it
larger if you ran into overflows.
--
Jens Axboe
prev parent reply other threads:[~2023-03-15 19:10 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
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 [this message]
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