LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
Dan Schatzberg <schatzberg.dan@gmail.com>
Subject: Re: [PATCH V4 0/7] loop: cleanup charging io to mem/blkcg
Date: Mon, 9 Aug 2021 08:41:59 +0200 [thread overview]
Message-ID: <20210809064159.GA19070@lst.de> (raw)
In-Reply-To: <20210806080302.298297-1-ming.lei@redhat.com>
FYI, I am still of the firm opinion that the current cgroup support in
the loop driver needs to be reverted and be redone cleanly from scratch
without impacting the normal non-cgroup path at all.
On Fri, Aug 06, 2021 at 04:02:55PM +0800, Ming Lei wrote:
> Hello Guys,
>
> Cleanup charging io to mem/blkcg a bit:
>
> - avoid to store blkcg_css/memcg_css in loop_cmd, and store blkcg_css in
> loop_worker instead
>
> - avoid to acquire ->lo_work_lock in IO path
>
> - simplify blkcg_css query via xarray
>
> - other misc cleanup
>
> V4:
> - fix build failure in case of !CONFIG_CGROUPS: changed to use
> 'struct cgroup_subsys_state' as parameter of the added memcg helper;
> meantime add helper loop_blkcg_css_id()
>
> V3:
> - one patch style change in 7/7
> - rebase patch 4/7 against for-5.15/block
> - add acked-by tag
>
> V2:
> - add helper of memcg_get_e_css
> - cleanup #ifdef
> - improve the last patch, as discussed with Dan Schatzberg
>
>
> Ming Lei (7):
> mm: memcontrol: add helper of memcg_get_e_css
> loop: clean up blkcg association
> loop: conver timer for monitoring idle worker into dwork
> loop: add __loop_free_idle_workers() for covering freeing workers in
> clearing FD
> loop: improve loop_process_work
> loop: use xarray to store workers
> loop: don't add worker into idle list
>
> drivers/block/loop.c | 331 +++++++++++++++++++++----------------
> drivers/block/loop.h | 7 +-
> include/linux/memcontrol.h | 10 ++
> 3 files changed, 201 insertions(+), 147 deletions(-)
>
> --
> 2.31.1
---end quoted text---
next prev parent reply other threads:[~2021-08-09 6:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 8:02 Ming Lei
2021-08-06 8:02 ` [PATCH V4 1/7] mm: memcontrol: add helper of memcg_get_e_css Ming Lei
2021-08-12 8:58 ` Christoph Hellwig
2021-08-06 8:02 ` [PATCH V4 2/7] loop: clean up blkcg association Ming Lei
2021-08-12 8:59 ` Christoph Hellwig
2021-08-06 8:02 ` [PATCH V4 3/7] loop: conver timer for monitoring idle worker into dwork Ming Lei
2021-08-06 8:02 ` [PATCH V4 4/7] loop: add __loop_free_idle_workers() for covering freeing workers in clearing FD Ming Lei
2021-08-06 8:03 ` [PATCH V4 5/7] loop: improve loop_process_work Ming Lei
2021-08-06 8:03 ` [PATCH V4 6/7] loop: use xarray to store workers Ming Lei
2021-08-06 8:03 ` [PATCH V4 7/7] loop: don't add worker into idle list Ming Lei
2021-08-09 6:41 ` Christoph Hellwig [this message]
2021-08-10 3:26 ` [PATCH V4 0/7] loop: cleanup charging io to mem/blkcg Ming Lei
2021-08-12 9:00 ` Christoph Hellwig
2021-08-14 9:12 ` Ming Lei
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=20210809064159.GA19070@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=schatzberg.dan@gmail.com \
--subject='Re: [PATCH V4 0/7] loop: cleanup charging io to mem/blkcg' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).