| 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
| ||
|
Message-ID: <48C9C7FD.3060609@users.sourceforge.net> Date: Thu, 11 Sep 2008 21:38:05 -0400 From: Elad Lahav <elad_lahav@...rs.sourceforge.net> To: linux-kernel@...r.kernel.org Subject: Soft IRQ statistics under /proc/stat I've been observing some oddities in the statistics produced by mpstat with respect to soft IRQs (for example, considerable soft IRQ time on processors sending UDP packets on dummy NICs). While looking at the kernel code, I noticed that ticks are attributed to soft IRQs when softirq_count() is greater than 0. This happens in __local_bh_disable(), which is called from __do_softirq(), but also from local_bh_disable(). Thus, the number of ticks reported in /proc/stat refers to any execution path that runs with soft IRQs disabled, not just code called from __do_softirq(). I hacked the kernel to differentiate between the two cases, and indeed the anomalies I saw can be explained as code executing under local_bh_disable(). Is this behaviour by design? References to /proc/stat on the web refer to this number simply as "soft IRQ time" (e.g., http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/en-US/Reference_Guide/s2-proc-stat.html). I would have expected that to include only execution paths starting from __do_softirq(). Elad -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists