Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 11 Mar 2003 19:27:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 11 Mar 2003 19:26:42 -0500 Received: from pizda.ninka.net ([216.101.162.242]:58089 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Tue, 11 Mar 2003 19:23:38 -0500 Date: Tue, 11 Mar 2003 16:34:08 -0800 (PST) Message-Id: <20030311.163408.124083653.davem@redhat.com> To: shemminger@osdl.org Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org, linux-net@vger.kernel.org Subject: Re: [PATCH] (8/8) Kill brlock From: "David S. Miller" In-Reply-To: <1047429105.15875.123.camel@dell_ss3.pdx.osdl.net> References: <1047428123.15872.113.camel@dell_ss3.pdx.osdl.net> <20030311.162323.94095868.davem@redhat.com> <1047429105.15875.123.camel@dell_ss3.pdx.osdl.net> X-FalunGong: Information control. X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 770 Lines: 15 From: Stephen Hemminger Date: 11 Mar 2003 16:31:46 -0800 The caller's didn't need to stop packet processing, just remove their type from a list or some other call back hook. A simple pointer update takes care of removing a simple call back. The list delete rcu code takes care of the memory barriers and doing the updates in the right order. This ensures no future packet processing will grab that token Ok, I'm fine with this then. Linus you can apply all of his patches. - 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/