From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753289AbYKMRZl (ORCPT ); Thu, 13 Nov 2008 12:25:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751066AbYKMRZc (ORCPT ); Thu, 13 Nov 2008 12:25:32 -0500 Received: from one.firstfloor.org ([213.235.205.2]:40252 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750893AbYKMRZb (ORCPT ); Thu, 13 Nov 2008 12:25:31 -0500 Date: Thu, 13 Nov 2008 18:34:51 +0100 From: Andi Kleen To: Steven Rostedt Cc: Andi Kleen , =?iso-8859-1?Q?Fr=E9d=E9ric?= Weisbecker , Ingo Molnar , Linux Kernel Subject: Re: [PATCH 1/2] tracing/function-return-tracer: Make the function return tracer lockless Message-ID: <20081113173451.GY3810@one.firstfloor.org> References: <491B4F0A.3080901@gmail.com> <87od0jd6ds.fsf@basil.nowhere.org> <20081113171220.GX3810@one.firstfloor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > So the answer to this is: > > i = index++; > barrier(); > write to index i (not index); That was my first thought when I wrote the original email, but the disadvantage is that barrier() is a big hammer that flushes everything and can make the code much worse. That is why I suggested local_add_return() instead. -Andi -- ak@linux.intel.com