[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101203164844.GB235120@jupiter.n2.diac24.net>
Date: Fri, 3 Dec 2010 17:48:44 +0100
From: David Lamparter <equinox@...c24.net>
To: Ben Hutchings <bhutchings@...arflare.com>
Cc: David Lamparter <equinox@...c24.net>,
Mahesh Bandewar <maheshb@...gle.com>,
linux-netdev <netdev@...r.kernel.org>,
Tom Herbert <therbert@...gle.com>,
David Miller <davem@...emloft.net>
Subject: Re: [PATCH v2] ethtool : Allow ethtool to set interface in loopback
mode.
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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists