[E1000-devel] e1000/igb modules are not getting parameters from modprobe.conf at boot time

[More, A. <and...@in...>]

Hi,

I've noted the following weird behavior with the e1000 and igb drivers
on RH4U5 and RH5U1.

As I'm working with High Performance Computing clusters, I would like to
disable ITR to decrease latency on short messages.

I've used the following line on /etc/modprobe.conf.

options e1000 InterruptThrottleRate=0,0 TxIntDelay=0,64
RxAbsIntDelay=0,128 TxAbsIntDelay=0,64

However when testing the latency I'm only having the expected behaviour
after manually reloading the modules. It's like at boot time the module
parameters are not took in account.

Values range from 25 to 50 us after booting and then they keep around 19
after module reload. (a plain 'modprobe -r igb;modprobe igb' to force
the reload).

I couldn't reproduce this issue on SLES10 SP1, it's only happening on
RH.
My first guess was bad init scripts on RH but it seems that the kernel
is using modprobe on-the-fly to load this kind of device drivers.

Any ideas?

Thanks!

-- Andres