linux-kernel - Re: [PATCH linux-next] delayacct: track delays from IRQ/SOFTIRQ

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20230411065109.172037-1-yang.yang29@zte.com.cn>
Date:   Tue, 11 Apr 2023 14:51:09 +0800
From:   Yang Yang <yang.yang29@....com.cn>
To:     akpm@...ux-foundation.org
Cc:     a.p.zijlstra@...llo.nl, bsingharora@...il.com, corbet@....net,
        juri.lelli@...hat.com, linux-doc@...r.kernel.org,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, mingo@...hat.com, yang.yang29@....com.cn,
        wang.yong12@....com.cn, huang.junhua@....com.cn,
        jiang.xuexin@....com.cn
Subject: Re: [PATCH linux-next] delayacct: track delays from IRQ/SOFTIRQ

> We're somewhat double-accounting.  Delays due to, for example, IO will
> already include delays from IRQ activity.  But it's presumably a minor
> thing and I don't see why anyone would care.

Thanks for your reviewing! I also think double-accounting should be OK, some
one who is tunning IO or IRQ could focus on the related delay respectively.
And PSI has the same logic when calculate IRQ or IO pressure.