On Fri, 2012-07-20 at 11:56 -0400, Don Dutile wrote: > On 07/20/2012 11:27 AM, Chris Friesen wrote: > > On 07/17/2012 03:11 PM, David Miller wrote: > >> From: Chris Friesen<chris.friesen@xxxxxxxxxxx> > >> Date: Tue, 17 Jul 2012 15:08:45 -0600 > >> > >>> From that perspective a sysfs-based interface is ideal since it is > >>> directly scriptable. > >> > >> As is anything ethtool or netlink based, since we have 'ethtool' > >> and 'ip' for scripting. > > > > I'm not picky...whatever works. > > > > To me the act of creating virtual functions seems generic enough (I'm aware of SR-IOV capable storage controllers, I'm sure there is other hardware as well) that ethtool/ip don't really seem like the most appropriate tools for the job. > > > Yes, and then there are 'other network' controllers too ... IB which > I don't know if it adheres to ethtool, since it's not an Ethernet > device ... isn't that why they call it Infiniband ... ;-) ) > In the telecom space, they use NTBs and PCI as a 'network' ... I know, > not common in Linux space, and VFs in that space aren't being > discussed (that I've ever heard), but another example where > 'network' != Ethernet, so ethtool doesn't solve PCI-level > configuration/use. [...] The ethtool API is typically used for net device operations that can be largely devolved to individual drivers, and which the network stack can mostly ignore (though offload features are an historical exception to this). It started with Ethernet link settings, but many operations are applicable (and implemented by) other types of network device. Ben. -- Ben Hutchings, Staff Engineer, Solarflare Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked. -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
