From: Jens Axboe <[email protected]>
To: [email protected]
Subject: [PATCHES 0/3] Mem accounting and IRQ req cache
Date: Wed, 10 Feb 2021 08:16:01 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
This builds on the stuff that Pavel and I have been tossing around:
Patch 1: Enable req cache for the last class of requests, those that end
up completing from IRQ context. That's regular file/bdev reads
and writes.
Patch 2: Enable SLAB_ACCOUNT/memcg accounting for requests
Patch 3: Use memcg for the ring array accounting as well. That moves it
outside of rlimit memlock, though we retain memlock accounting
for registered buffers.
--
Jens Axboe
next reply other threads:[~2021-02-10 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 15:16 Jens Axboe [this message]
2021-02-10 15:16 ` [PATCH 1/3] io_uring: enable req cache for IRQ driven IO Jens Axboe
2021-02-10 15:16 ` [PATCH 2/3] io_uring: enable kmemcg account for io_uring requests Jens Axboe
2021-02-10 15:16 ` [PATCH 3/3] io_uring: place ring SQ/CQ arrays under memcg memory limits 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] \
/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