mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Usama Arif <usama.arif@linux.dev>
To: Tejun Heo <tj@kernel.org>
Cc: axboe@kernel.dk, cgroups@vger.kernel.org, josef@toxicpanda.com,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	hannes@cmpxchg.org, mkoutny@suse.com, shakeel.butt@linux.dev,
	riel@surriel.com
Subject: Re: [PATCH] blk-cgroup: skip rstat flush for cgroups without blkgs
Date: Thu, 17 Sep 2026 18:41:32 +0100	[thread overview]
Message-ID: <7d5f54bc-6daa-45c3-b57b-23d3204d3e7e@linux.dev> (raw)
In-Reply-To: <aqwV9cjg7Yj2OtBG@slm.duckdns.org>



On 17/09/2026 17:31, Tejun Heo wrote:
> On Thu, Sep 17, 2026 at 09:10:20AM -0700, Usama Arif wrote:
>> Non-root io.stat reads flush the blkcg rstat subtree before walking
>> ->blkg_list. This takes the subsystem rstat lock and checks for pending
>> updates on every possible CPU, even when there is no per-device state to
>> print.
>>
>> Blkg creation is hierarchical. A descendant blkg implies an ancestor
>> blkg on the same device, so an empty ->blkg_list means the subtree cannot
>> contribute any output. Return early in that case.
>>
>> A concurrent first blkg may be deferred to the next read. This is
>> consistent with the existing non-atomic flush and list walk.
>>
>> This is not rare: 340 of 969 io.stat files were empty on a 316-CPU host.
>> In a 16-vCPU lockdep-enabled guest, the median
> 
> Can you please test on a kernel w/ lockdep disabled? It doesn't make much
> sense to compare performance numbers with lockdep enabled.
> 

The updated numbers without lockdep are:

                             before    after
      empty io.stat           7.02 us   5.47 us
      populated io.stat       7.84 us   7.83 us

    The median paired reduction for empty reads was 22.1% (20.0-22.4% across
    pairs). System CPU time per read fell by 22.8%. Populated reads showed no
    consiste



>> open/read/close time over 35 batches of 20,000 reads changed as follows:
>>
>>                          before     after
>>   empty io.stat          49.1 us   41.0 us
>>   populated io.stat      49.9 us   50.2 us
>>
>> This is a 16.6% reduction for empty reads. Populated reads were unchanged
>> within measurement noise.
>>
>> Signed-off-by: Usama Arif <usama.arif@linux.dev>
> 
> That said, I don't see any downsides:
> 
> Acked-by: Tejun Heo <tj@kernel.org>
> 
> Thanks.
> 


      reply	other threads:[~2026-09-17 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 16:10 Usama Arif
2026-09-17 16:31 ` Tejun Heo
2026-09-17 17:41   ` Usama Arif [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=7d5f54bc-6daa-45c3-b57b-23d3204d3e7e@linux.dev \
    --to=usama.arif@linux.dev \
    --cc=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkoutny@suse.com \
    --cc=riel@surriel.com \
    --cc=shakeel.butt@linux.dev \
    --cc=tj@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

all inboxes | Powered by JetHome®