[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080630.214223.53060905.davem@davemloft.net>
Date: Mon, 30 Jun 2008 21:42:23 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: rdreier@...co.com
Cc: andi@...stfloor.org, Santwona.Behera@....COM,
netdev@...r.kernel.org, jeff@...zik.org, Matheos.Worku@....COM,
Michael.Speer@....COM, gkernel-commit@...ts.sourceforge.net
Subject: Re: [PATCH 0/3] Add support for rx flow hash configuration in a
network device
From: Roland Dreier <rdreier@...co.com>
Date: Mon, 30 Jun 2008 20:33:45 -0700
> > We've discussed this before and Jeff Garzik and I already told
> > everyone that we want to make this configurable and ethtool is
> > the way to do it no matter how adhoc and device specific the
> > interfaces might end up being.
>
> I think it was a few weeks ago that Jeff said:
>
> I know user interfaces are annoying because you have to think about
> chips other than your own, but that's life. Other hardware vendors have
> to do it too.
>
> Letting each driver have a different user interface is /unfriendly/ to
> both developers users.
>
> I guess as long as you stick an "ethtool" in front of the different
> interfaces it all becomes OK.
This interface we're talking about is in fact not all that device
specific, and it's extensible so that we can describe different types
of flow hashing types if so needed to support other chips.
Currently Sun's Neptune is the only one that offers so many options,
and to be honest I expect other implementations to be subsets of what
Neptune can do.
--
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