Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752608AbYKGUEO (ORCPT ); Fri, 7 Nov 2008 15:04:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751422AbYKGUD5 (ORCPT ); Fri, 7 Nov 2008 15:03:57 -0500 Received: from relais.videotron.ca ([24.201.245.36]:54701 "EHLO relais.videotron.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751324AbYKGUD4 (ORCPT ); Fri, 7 Nov 2008 15:03:56 -0500 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: TEXT/PLAIN; charset=US-ASCII Date: Fri, 07 Nov 2008 15:03:49 -0500 (EST) From: Nicolas Pitre X-X-Sender: nico@xanadu.home To: Andrew Morton Cc: David Howells , Mathieu Desnoyers , Linus Torvalds , Ingo Molnar , Peter Zijlstra , linux-kernel@vger.kernel.org, Ralf Baechle , benh@kernel.crashing.org, paulus@samba.org, David Miller , Ingo Molnar , Thomas Gleixner , Steven Rostedt , linux-arch@vger.kernel.org Subject: Re: [RFC patch 08/18] cnt32_to_63 should use smp_rmb() In-reply-to: <20081107092115.7c3c4a49.akpm@linux-foundation.org> Message-id: References: <20081107003816.9b0f947a.akpm@linux-foundation.org> <20081107052336.652868737@polymtl.ca> <20081107053349.861709786@polymtl.ca> <20081106220530.5b0e3a96.akpm@linux-foundation.org> <25363.1226056819@redhat.com> <20081107075003.fa93ccf4.akpm@linux-foundation.org> <20081107092115.7c3c4a49.akpm@linux-foundation.org> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1650 Lines: 43 On Fri, 7 Nov 2008, Andrew Morton wrote: > On Fri, 07 Nov 2008 11:47:47 -0500 (EST) Nicolas Pitre wrote: > > > > btw, do you know how damned irritating and frustrating it is for a code > > > reviewer to have his comments deliberately ignored and deleted in > > > replies? > > > > Do you know how irritating and frustrating it is when reviewers don't > > care reading the damn comments along with the code? > > As you still seek to ignore it, I shall repeat my earlier question. > Please do not delete it again. > > It apparently tries to avoid races via ordering tricks, as long > as it is called with sufficient frequency. But nothing guarantees > that it _is_ called sufficiently frequently? > > Things like tickless kernels and SCHED_RR can surely cause > sched_clock() to not be called for arbitrary periods. On the machines this was initially written for, the critical period is in the order of minutes. And if you're afraid you might lack enough scheduling activities for that long, you simply have to keep the algorithm "warm" with a simple kernel timer which only purpose is to ensure it is called often enough. > Userspace cli() will definitely do this, but it is expected to break > stuff and is not as legitiate a thing to do. Why do you bring it on then? > I'm just giving up on the tastefulness issue. Taste is a pretty subjective matter. Nicolas -- 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/