From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH 3/16] Spidernet RX Locking Date: Thu, 07 Dec 2006 05:09:20 -0500 Message-ID: <4577E850.6040500@pobox.com> References: <20061206223223.GH17931@austin.ibm.com> <20061206233134.GC4649@austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andrew Morton , netdev@vger.kernel.org, linuxppc-dev@ozlabs.org, James K Lewis , Arnd Bergmann , Geoff Levand Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:36212 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031931AbWLGKJ1 (ORCPT ); Thu, 7 Dec 2006 05:09:27 -0500 To: Linas Vepstas In-Reply-To: <20061206233134.GC4649@austin.ibm.com> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Linas Vepstas wrote: > The RX packet handling can be called from several > places, yet does not protect the rx ring structure. > This patch places the ring buffer pointers under a lock. > > Signed-off-by: Linas Vepstas > Cc: James K Lewis > Cc: Arnd Bergmann This is a HUGELY invasive patch. A sledgehammer. What /specifically/ are these "several places", and what other non-sledgehammer approaches were discarded before arriving at this one? Jeff