linux-kernel - Re: [PATCH] hrtimers: Special-case zero length sleeps

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20120215145857.GA21755@srcf.ucam.org>
Date:	Wed, 15 Feb 2012 14:58:58 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: [PATCH] hrtimers: Special-case zero length sleeps

Regardless of whether userspace should be concerning itself about this 
kind of thing or not, there's plenty of userspace that calls sleep(0) on 
the assumption that it'll get rescheduled. This makes using whole-system 
timer slack difficult, because there are some applications that do this 
even if they're event-driven and sleeping for significant lengths of 
time here breaks them. I'd certainly understand the argument for fixing 
userspace instead, but that's a massive task for something that's easily 
special-cased in the kernel.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/