From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexandre Negrel <alexandre@negrel.dev>
Subject: Re: [PATCH v2] io_uring: drop overflowing CQE instead of exceeding memory limits
Date: Tue, 30 Dec 2025 18:50:59 -0700 [thread overview]
Message-ID: <176714585945.414491.8962578639891621014.b4-ty@kernel.dk> (raw)
In-Reply-To: <20251230190909.557152-1-alexandre@negrel.dev>
On Tue, 30 Dec 2025 19:57:28 +0100, Alexandre Negrel wrote:
> Allocate the overflowing CQE with GFP_NOWAIT instead of GFP_ATOMIC. This
> changes causes allocations to fail in out-of-memory situations,
> resulting in CQE being dropped. Using GFP_ATOMIC allows a process to
> exceed memory limits.
>
>
Applied, thanks!
[1/1] io_uring: drop overflowing CQE instead of exceeding memory limits
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-12-31 1:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 18:57 [PATCH v2] io_uring: drop overflowing CQE instead of exceeding memory limits Alexandre Negrel
2025-12-31 1:50 ` 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 \
--in-reply-to=176714585945.414491.8962578639891621014.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=alexandre@negrel.dev \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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