netdev - Re: [PATCH 0/3] Add support for rx flow hash configuration in a network device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <adaabh2ffc6.fsf@cisco.com>
Date:	Mon, 30 Jun 2008 20:33:45 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	David Miller <davem@...emloft.net>
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

 > 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.

 - R.
--
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