>-----Original Message-----
>From: Xu, Gang 1. (NSN - CN/Hangzhou)
>[mailto:[email protected]]
>Sent: Sunday, June 08, 2014 10:52 PM
>To: [email protected]
>Cc: Ni, Zhenglin (NSN - CN/Hangzhou); Liu, Xin 9. (NSN -
>CN/Hangzhou); Ouyang, Lane (NSN - CN/Hangzhou); Yan, Liming
>(NSN - CN/Hangzhou); Liu, Zuofeng (NSN - CN/Hangzhou)
>Subject: [E1000-devel] Need Help about UDP multiple receive
>queue
>
>Hi,
>
>     We try to enable the UDP multiple receiving queue by
>"ethtool -N fi0 rx-flow-hash udp4 sdfn" command,
>but after this command executed, all udp packets with
>different soured udp port still allocated to the same rx
>queue 0. Other rx queues are nearly empty, and then this
>only processed by one CPU core(load 100%) and other cores
>are nearly 0, we can not get the maximum packets through
>out.
>
>Our question:
>1.      How to assign the udp packets with different udp
>source ports to different rx queues ?

The command you used above should work, however keep in mind that only packets 
that are not fragmented will be given an RSS hash by the HW. You can check your 
traffic via tcpdump - if your UDP packets are fragmented they will not be 
assigned different queues by RSS.

Some things you may be able to do is increase the MTU, or in the case of 
multicast (if you are doing receives only) you can have the transmitting app 
spoof the src port in order to generate a different hash for each packet 
(because the dst IP/port info is lost for the HW if the packet is fragmented).

Thanks,
Emil


------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to