From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Lamparter Subject: Re: [PATCH v2] ethtool : Allow ethtool to set interface in loopback mode. Date: Fri, 3 Dec 2010 17:48:44 +0100 Message-ID: <20101203164844.GB235120@jupiter.n2.diac24.net> References: <1291299660.3259.5.camel@bwh-desktop> <20101203160333.GA235120@jupiter.n2.diac24.net> <1291394014.13384.7.camel@bwh-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: David Lamparter , Mahesh Bandewar , linux-netdev , Tom Herbert , David Miller To: Ben Hutchings Return-path: Received: from spaceboyz.net ([87.106.131.203]:32996 "EHLO spaceboyz.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751992Ab0LCQtO (ORCPT ); Fri, 3 Dec 2010 11:49:14 -0500 Content-Disposition: inline In-Reply-To: <1291394014.13384.7.camel@bwh-desktop> Sender: netdev-owner@vger.kernel.org List-ID: On Fri, Dec 03, 2010 at 04:33:34PM +0000, Ben Hutchings wrote: > On Fri, 2010-12-03 at 17:03 +0100, David Lamparter wrote: > > On Thu, Dec 02, 2010 at 02:35:51PM -0800, Mahesh Bandewar wrote: > > > This patch adds -L command-line option to switch loopback mode on/off > > > and -l option to display current loopback mode on a specified interface. > > [...] > > > +.A1 on off > > > +Switches loopback mode > > > +.B on > > > +or > > > +.B off > > > > What about devices that support different kinds of loopback, like MAC > > loopback & PHY loopback? (No idea if we have kernel support for this > > either...) > > That distinction is useful for diagnostic purposes, but drivers can > already cover those different loopback modes in self-test. The > motivation for this feature is testing data path behaviour, and Mahesh > has specified that loopback should be enabled as near as possible to the > host. Ah, good enough. Thanks. -David