>-Original Message-
>From: Jeff Garzik [mailto:[EMAIL PROTECTED]
>Veeraiyan, Ayyappan wrote:
>> So, with driver/device supporting multiple Tx and Rx queues, I think,
it
>> would be very useful to have ethtool interface to manage the number
of
>> Tx and Rx queues of the interface.
>
>
>Absol
Veeraiyan, Ayyappan wrote:
So, with driver/device supporting multiple Tx and Rx queues, I think, it
would be very useful to have ethtool interface to manage the number of
Tx and Rx queues of the interface.
Absolutely! ethtool patches welcome :)
git://git.kernel.org/pub/scm/network/ethtool/et
>-Original Message-
>From: Jeff Garzik [mailto:[EMAIL PROTECTED]
>
>Stephen Hemminger wrote:
>> Using module parameter for per device settings is bad idea.
>> Please extend existing interfaces like ethtool, etc rather than
>committing
>> to a bad inflexible API.
>
>
>I agreed with Stephen's
Stephen Hemminger wrote:
Using module parameter for per device settings is bad idea.
Please extend existing interfaces like ethtool, etc rather than committing
to a bad inflexible API.
I agreed with Stephen's comments here.
In general, net driver policy is to use ethtool (per-interface
granu
+
+Command Line Parameters
+===
+
+If the driver is built as a module, the following optional parameters are
+used by entering them on the command line with the modprobe command using
+this syntax:
+
+ modprobe ixgbe [=,,...]
+
+For example, with two PRO/10GbE PCI Expres
