From: Ben Hutchings <bhutchings@solarflare.com>
To: Mahesh Bandewar <maheshb@google.com>
Cc: David Miller <davem@davemloft.net>,
linux-netdev <netdev@vger.kernel.org>,
laurent chavey <chavey@google.com>
Subject: Re: [PATCH] Net-ethtool : Allow ethtool to set interface in loopback mode.
Date: Tue, 30 Nov 2010 19:15:07 +0000 [thread overview]
Message-ID: <1291144507.21077.56.camel@bwh-desktop> (raw)
In-Reply-To: <AANLkTikM4=yOu9L7h0FZUkmMNG-LVdGsdSLOLJmw2+UW@mail.gmail.com>
On Tue, 2010-11-30 at 11:05 -0800, Mahesh Bandewar wrote:
> On Tue, Nov 30, 2010 at 7:01 AM, Ben Hutchings
> <bhutchings@solarflare.com> wrote:
[...]
> > > diff --git a/include/linux/ethtool.h b/include/linux/ethtool.h
> > > index 6628a50..7523d45 100644
> > > --- a/include/linux/ethtool.h
> > > +++ b/include/linux/ethtool.h
> > > @@ -678,6 +678,8 @@ struct ethtool_ops {
> > > struct ethtool_rxfh_indir *);
> > > int (*set_rxfh_indir)(struct net_device *,
> > > const struct ethtool_rxfh_indir *);
> > > + int (*get_loopback)(struct net_device *, u32 *);
> > > + int (*set_loopback)(struct net_device *, u32);
> > > };
> > > #endif /* __KERNEL__ */
> > >
> > > @@ -741,6 +743,8 @@ struct ethtool_ops {
> > > #define ETHTOOL_GSSET_INFO 0x00000037 /* Get string set info */
> > > #define ETHTOOL_GRXFHINDIR 0x00000038 /* Get RX flow hash indir'n table */
> > > #define ETHTOOL_SRXFHINDIR 0x00000039 /* Set RX flow hash indir'n table */
> > > +#define ETHTOOL_SLOOPBACK 0x0000003a /* Enable / Disable Loopback */
> > [...]
> >
> > Where should loopback be done, when enabled? As near as possible to the
> > host, so it only covers the DMA engines, or as far away as possible, so
> > it covers most of the MAC/PHY hardware?
> >
> Putting it very close to the HW would stress the maximum soft path and
> would make it
> beneficial to more people / developers. I understand that capabilities
> offered by different
> NIC vendors vary so it's little difficult to draw the line as to where
> it should be done.
Of course, that's why I suggest 'as near/far as possible' rather than
trying to specify the exact point at which loopback would be enabled.
> So
> if the theme to "maximize the soft path" is maintained, we can leave
> it to the individual
> driver(s) to maximize the value in offering.
I think this should be specified, otherwise measurements on different
types of NIC will not be comparable. The ethtool API suffers greatly
from losse specification and resulting inconsistency between drivers.
So please add the comment that loopback should be enabled as near to the
host as possible.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-11-30 19:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 8:00 [PATCH] Net-ethtool : Allow ethtool to set interface in loopback mode Mahesh Bandewar
2010-11-30 9:48 ` Simon Horman
2010-11-30 15:01 ` Ben Hutchings
2010-11-30 19:05 ` Mahesh Bandewar
2010-11-30 19:15 ` Ben Hutchings [this message]
2010-11-30 21:22 ` Mahesh Bandewar
2010-11-30 23:57 ` [PATCH v2] " Mahesh Bandewar
2010-12-01 14:54 ` Ben Hutchings
2010-12-01 20:14 ` [PATCH v3] " Mahesh Bandewar
2010-12-01 20:17 ` Ben Hutchings
2010-12-10 4:11 ` David Miller
2011-01-05 0:30 ` [PATCH v2] net: " Mahesh Bandewar
2011-01-05 0:36 ` Stephen Hemminger
2011-01-05 1:21 ` Ben Hutchings
2011-01-05 1:29 ` Stephen Hemminger
2011-01-05 1:34 ` Rick Jones
2011-01-05 1:53 ` Stephen Hemminger
2011-01-05 1:59 ` Ben Hutchings
2011-01-05 2:06 ` Mahesh Bandewar
2011-01-05 1:39 ` Mahesh Bandewar
2011-01-05 16:22 ` Jeff Garzik
2011-01-06 22:13 ` Ben Hutchings
2011-01-07 0:47 ` Mahesh Bandewar
2011-01-07 1:30 ` Ben Hutchings
2011-01-12 19:24 ` Mahesh Bandewar
2011-01-22 0:23 ` [PATCH v4] net-next-2.6: " Mahesh Bandewar
2011-01-23 2:35 ` Ben Hutchings
2011-01-23 17:12 ` Mahesh Bandewar
2011-01-23 17:32 ` Michał Mirosław
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1291144507.21077.56.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=chavey@google.com \
--cc=davem@davemloft.net \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).