Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751242Ab2BOO7B (ORCPT ); Wed, 15 Feb 2012 09:59:01 -0500 Received: from cavan.codon.org.uk ([93.93.128.6]:33303 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750891Ab2BOO7A (ORCPT ); Wed, 15 Feb 2012 09:59:00 -0500 Date: Wed, 15 Feb 2012 14:58:58 +0000 From: Matthew Garrett To: Peter Zijlstra Cc: Thomas Gleixner , LKML , Arjan van de Ven Subject: Re: [PATCH] hrtimers: Special-case zero length sleeps Message-ID: <20120215145857.GA21755@srcf.ucam.org> References: <1317308372-6810-1-git-send-email-mjg@redhat.com> <1329317650.2293.129.camel@twins> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1329317650.2293.129.camel@twins> User-Agent: Mutt/1.5.20 (2009-06-14) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: mjg59@cavan.codon.org.uk X-SA-Exim-Scanned: No (on cavan.codon.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 827 Lines: 16 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@srcf.ucam.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/