| 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: <alpine.LSU.2.00.0903121541410.8068@fbirervta.pbzchgretzou.qr> Date: Thu, 12 Mar 2009 15:45:46 +0100 (CET) From: Jan Engelhardt <jengelh@...ozas.de> To: Arjan van de Ven <arjan@...radead.org> cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: System tick rate On Thursday 2009-03-12 15:21, Arjan van de Ven wrote: >On Thu, 12 Mar 2009 14:38:19 +0100 (CET) Jan Engelhardt wrote: >> >> is there an "official" way of obtaining the current tick rate when >> CONFIG_NO_HZ? > >what does "current tick rate" mean for you in a no-hz situation ? >is it the HZ value (which is supposed to be invisible from userspace, >so good luck) or the wakeup count ? Hm, I guess what I want is the number of timer interrupts which occurred within the observation period that called the scheduler code. (So that excludes RTC on usual x86en.) -- 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