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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <EA929A9653AAE14F841771FB1DE5A1365FE4B3E600@rrsmsx501.amr.corp.intel.com>
Date:	Thu, 25 Mar 2010 11:33:53 -0600
From:	"Tantilov, Emil S" <emil.s.tantilov@...el.com>
To:	Jeff Garzik <jeff@...zik.org>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH] e1000e: export some settings using ethtool private flags

Jeff Garzik wrote:
> On 03/25/2010 01:16 PM, Tantilov, Emil S wrote:
>> Jeff Garzik wrote:
>>> The ethtool private flags interface exists to get/set
>>> driver-specific settings at runtime, in a flexible manner.
>>> 
>>> Use this facility to export a couple e1000e features, that were
>>> previously only set at module initialization time.
>>> 
>>> Signed-off-by: Jeff Garzik<jgarzik@...hat.com>
>>> ---
>>>   drivers/net/e1000e/ethtool.c |   27 +++++++++++++++++++++++++++
>>>   1 file changed, 27 insertions(+)
>> 
>> Jeff,
>> 
>> What is the use case for the ethtool private flags?
> 
> It is stated in the changelog above :)  It enables feature setting at
> setting, on an easy, per-network-interface basis, that were previously
> only settable at module initialization (ie. load) time.
> 
> 
>> At least I don't see an option in ethtool that would make use of
>> them. 
> 
> This is added in a separate patch, since the above patch is the first
> to make use of the private-flags ethtool mechanism.

Can you point me to it? It would really help me with testing.

Thanks,
Emil


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

Powered by Openwall GNU/*/Linux Powered by OpenVZ