Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755357Ab2BOUWY (ORCPT ); Wed, 15 Feb 2012 15:22:24 -0500 Received: from cavan.codon.org.uk ([93.93.128.6]:59550 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755080Ab2BOUWX (ORCPT ); Wed, 15 Feb 2012 15:22:23 -0500 Date: Wed, 15 Feb 2012 20:22:21 +0000 From: Matthew Garrett To: Thomas Gleixner Cc: LKML , Arjan van de Ven , Peter Zijlstra Subject: Re: [PATCH] hrtimers: Special-case zero length sleeps Message-ID: <20120215202221.GA29552@srcf.ucam.org> References: <1317308372-6810-1-git-send-email-mjg@redhat.com> <20120215145225.GA21448@srcf.ucam.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: 914 Lines: 21 On Wed, Feb 15, 2012 at 09:14:30PM +0100, Thomas Gleixner wrote: > Just for the extended fun of it: The pre hrtimer implementation in > Linux put the task on sleep as well up to the next jiffies boundary, > so anything which used sleep(0) on a pre hrtimer kernel was going to > sleep. That's also the case today when high resolution timers are > disabled (compile or runtime). > > So anything which relies on sleep(0) as a fast scheduling point is and > has been broken forever. Excellent. So the real question is what /should/ sleep(0) do - nothing, schedule or sleep for an arbitrary period of time that could be years? -- 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/