Hi Amir the number of rx queues is determined loading the driver or at runtime with ethtool ‘combined’ as you can see at:
https://github.com/ntop/PF_RING/blob/dev/drivers/intel/i40e/i40e-2.4.6-zc/src/load_driver.sh#L39 <https://github.com/ntop/PF_RING/blob/dev/drivers/intel/i40e/i40e-2.4.6-zc/src/load_driver.sh#L39> Please also make sure that you are actually unloading the old driver before running insmod (maybe the new insmod is failing) Alfredo > On 10 Jul 2018, at 15:46, Amir Kaduri <[email protected]> wrote: > > Do the rx queues of an interface are determined only when loading the kernel > driver, or is there another thing that affects that? > > My problem is that I get a number that differs than what I think should be > (because maybe something during the machine boot doesn't work properly) > > For example: > What I assume our load script do is "insmod > /usr/local/pfring/drivers/intel/i40e.ko RSS=12,12,12,12,12,12,12,12" > What I actually get when I run "cat /proc/net/pf_ring/dev/eth4/info" > is "RX Queues: 14" (from previous reboot). > > So maybe the "insmod" doesn't actually work as expected, or is there anything > else that I'm not aware of? > > A'ii appreciate any help. > > Thanks > > _______________________________________________ > Ntop-misc mailing list > [email protected] > http://listgateway.unipi.it/mailman/listinfo/ntop-misc
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Ntop-misc mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-misc
