Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 17 Feb 2003 03:08:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 17 Feb 2003 03:08:45 -0500 Received: from are.twiddle.net ([64.81.246.98]:27031 "EHLO are.twiddle.net") by vger.kernel.org with ESMTP id ; Mon, 17 Feb 2003 03:05:55 -0500 Date: Mon, 17 Feb 2003 00:15:44 -0800 From: Richard Henderson To: Zwane Mwaikambo Cc: Ivan Kokshaysky , Linux Kernel , Linus Torvalds Subject: Re: [PATCH][2.5] Protect smp_call_function_data w/ spinlocks on Alpha Message-ID: <20030217001544.A13101@twiddle.net> Mail-Followup-To: Zwane Mwaikambo , Ivan Kokshaysky , Linux Kernel , Linus Torvalds References: <20030214175332.A19234@jurassic.park.msu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from zwane@holomorphy.com on Fri, Feb 14, 2003 at 12:16:12PM -0500 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 862 Lines: 21 On Fri, Feb 14, 2003 at 12:16:12PM -0500, Zwane Mwaikambo wrote: > Ok the reason being is that the lock not only protects the > smp_call_function_data pointer but also acts as a lock for that critical > section. Without it you'll constantly be overwriting the pointer halfway > through IPI acceptance (or even worse whilst a remote CPU is assigning the > data members). Really. Show me the sequence there? I happen to like the pointer_lock a lot, and think we should make more use of it on systems known to have cmpxchg. It saves on the number of cache lines that have to get bounced between processors. r~ - 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/