From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Hutchings Subject: Re: [PATCH 0/2] pktgen: Clone skb to avoid corruption of skbs in ndo_start_xmit methods (v3) Date: Mon, 22 Aug 2011 17:17:37 +0100 Message-ID: <1314029857.2803.6.camel@bwh-desktop> References: <1311105179-26408-1-git-send-email-nhorman@tuxdriver.com> <1311696338-4739-1-git-send-email-nhorman@tuxdriver.com> <1313593637.2776.9.camel@bwh-desktop> <20110822002641.GA2550@neilslaptop.think-freely.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: Neil Horman Return-path: Received: from exchange.solarflare.com ([216.237.3.220]:7202 "EHLO exchange.solarflare.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751974Ab1HVQRl (ORCPT ); Mon, 22 Aug 2011 12:17:41 -0400 In-Reply-To: <20110822002641.GA2550@neilslaptop.think-freely.org> Sender: netdev-owner@vger.kernel.org List-ID: On Sun, 2011-08-21 at 20:27 -0400, Neil Horman wrote: > On Wed, Aug 17, 2011 at 04:07:17PM +0100, Ben Hutchings wrote: > > On Tue, 2011-07-26 at 12:05 -0400, Neil Horman wrote: > > > Ok, after considering all your comments, Dave suggested this as an alternate > > > approach: > > > > > > 1) We create a new priv_flag, IFF_SKB_TX_SHARED, to identify drivers capable of > > > handling shared skbs. Default is to not set this flag > > > > > > 2) Modify ether_setup to enable this flag, under the assumption that any driver > > > calling this function is initalizing a real ethernet device and as such can > > > handle shared skbs since they don't tend to store state in the skb struct. > > > Pktgen can then query this flag when a user script attempts to issue the > > > clone_skb command and decide if it is to be alowed or not. > > [...] > > > > A bunch of Ethernet drivers do skb_pad() or skb_padto() in their > > ndo_start_xmit implementations, either to avoid hardware bugs or because > > the MAC doesn't automatically pad to the minimum frame length. This > > presumably means they can't generally handle shared skbs, though in the > > specific case of pktgen it should be safe as long as a single skb is not > > submitted by multiple threads at once. > > > Agreed, given that pktgen is doing skb sharing in a serialized manner (i.e. one > thread of execution increasing skb->users rather than in multiple threads), the > skb_pad[to] cases are safe. Are there cases in which shared skbs are > transmitted in parallel threads that we need to check for? Not that I'm aware of. However, you have defined the flag to mean 'safe to send shared skbs', and this is not generally true for those drivers. So please decide whether: a. The flag means 'safe to send shared skbs' (i.e. the TX path does not modify the skb) and drivers which pad must clear it on their devices. b. The flag means 'safe to send shared skbs in the way ptkgen does', and the restrictions this places on the user and driver should be specified. Ben. -- Ben Hutchings, Staff Engineer, Solarflare Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked.