netdev - Re: Should we report bus width/speed via ethtool?

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]

Date:	Wed, 05 Dec 2012 16:08:14 -0800
From:	Rick Jones <rick.jones2@...com>
To:	David Miller <davem@...emloft.net>
CC:	greearb@...delatech.com, netdev@...r.kernel.org,
	e1000-devel@...ts.sourceforge.net
Subject: Re: Should we report bus width/speed via ethtool?

On 12/05/2012 04:01 PM, David Miller wrote:
> lspci might be a good place to figure this out :-)  It's probably
> grovelling around in PCI config space to determine these things.

And if not lspci, "pcitop" used to grub around for such things, though 
its source may be rather moldy.  I'm sure though that if various chipset 
providers were willing to document their PCI performance counters, 
*someone* would be happy to bring pcitop into the present day...

happy benchmarking,

rick jones

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