Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753260AbYKGRWj (ORCPT ); Fri, 7 Nov 2008 12:22:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751080AbYKGRW3 (ORCPT ); Fri, 7 Nov 2008 12:22:29 -0500 Received: from smtp1.linux-foundation.org ([140.211.169.13]:52463 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750879AbYKGRW2 (ORCPT ); Fri, 7 Nov 2008 12:22:28 -0500 Date: Fri, 7 Nov 2008 09:21:15 -0800 From: Andrew Morton To: Nicolas Pitre 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() Message-Id: <20081107092115.7c3c4a49.akpm@linux-foundation.org> In-Reply-To: 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> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.5; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1176 Lines: 29 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. Userspace cli() will definitely do this, but it is expected to break stuff and is not as legitiate a thing to do. I'm just giving up on the tastefulness issue. -- 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/