From: Xiaoguang Wang <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Cc: [email protected]
Subject: Re: [PATCH] io_uring: set error code to be ENOMEM when io_alloc_async_ctx() fails
Date: Fri, 10 Apr 2020 00:01:44 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
hi,
> On 4/8/20 7:48 PM, Xiaoguang Wang wrote:
>> We should return ENOMEM for memory allocation failures, fix this
>> issue for io_alloc_async_ctx() calls.
>
> It's not uncommon to have out-of-memory turn into -EAGAIN for the
> application for runtime allocations, indicating that the application
> could feasibly try again and hope for a better outcome (maybe after
> freeing memory).
OK, i see, thanks.
>
> The error code is also documented as such in the io_uring_enter.2
> man page.
Yeah, I checked it just now, and I should read the man page carefully again :)
Regards,
Xiaoguang Wang
>
prev parent reply other threads:[~2020-04-09 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 2:48 [PATCH] io_uring: set error code to be ENOMEM when io_alloc_async_ctx() fails Xiaoguang Wang
2020-04-09 15:46 ` Jens Axboe
2020-04-09 16:01 ` Xiaoguang Wang [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 \
--in-reply-to=5329b498-c2a2-26d0-0e21-c91db9c8c68f@linux.alibaba.com \
[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