| 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: <20080521104131.GA4948@ucw.cz> Date: Wed, 21 May 2008 12:41:32 +0200 From: Pavel Machek <pavel@....cz> To: Thomas Gleixner <tglx@...utronix.de> Cc: Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org Subject: Re: better msleep for drivers Hi! > > Still longer term I suppose there's really no way around having accurate > > sleep functions and it's probably better to start testing earlier than later. > > No objections, but we should not do that with a stupid msleep > replacement interface; instead we should expose a flexible in kernel > variant of hrtimer_nanosleep() which lets the user utilize > ABS/REL_TIME and the different clocks. A msleep helper can be built on > top of this very easily. While you are at it... it would be cool to have 'mdelay(2500 msec), but it is okay to wait 100msec more' -- type interface, so we could use that for nohz benefit. Currently, mdelay is 'it is okay to wait 10msec more' interface, and it would be nice to have that explicit. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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