| 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: <1170948355.19743.41.camel@imap.mvista.com> Date: Thu, 08 Feb 2007 07:25:55 -0800 From: Daniel Walker <dwalker@...sta.com> To: mingo@...e.hu Cc: linux-kernel@...r.kernel.org Subject: scheduler timing After looking at the scheduler timing I was thinking it might be a fair trade off to convert sched_clock to return cycles instead of converting to nanosecond each time it reads .. I'm just probing for anyone thoughts on this .. I'm not promoting a specific implementation, but I would think the tuning nobs would have to stay in nanosecond, but everything else would be converted to cycles .. Daniel - 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