[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <65d9f79b-be9b-e21e-0624-5c9f2cc0c0b2@bytedance.com>
Date: Fri, 22 Jul 2022 11:30:53 +0800
From: Abel Wu <wuyun.abel@...edance.com>
To: Chengming Zhou <zhouchengming@...edance.com>, hannes@...xchg.org,
surenb@...gle.com, mingo@...hat.com, peterz@...radead.org,
tj@...nel.org, corbet@....net, akpm@...ux-foundation.org,
rdunlap@...radead.org
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
songmuchun@...edance.com, cgroups@...r.kernel.org
Subject: Re: [PATCH 9/9] sched/psi: add PSI_IRQ to track IRQ/SOFTIRQ pressure
Hi Chengming,
On 7/21/22 12:04 PM, Chengming Zhou Wrote:
> Now PSI already tracked workload pressure stall information for
> CPU, memory and IO. Apart from these, IRQ/SOFTIRQ could have
> obvious impact on some workload productivity, such as web service
> workload.
>
> When CONFIG_IRQ_TIME_ACCOUNTING, we can get IRQ/SOFTIRQ delta time
> from update_rq_clock_task(), in which we can record that delta
> to CPU curr task's cgroups as PSI_IRQ_FULL status.
The {soft,}irq affection should be equal to all the runnable tasks
on that cpu, not only rq->curr. Further I think irqstall is per-cpu
rather than per-cgroup.
Abel
Powered by blists - more mailing lists