Hey Fan, The issue is with our HW RSS doesn't work with frag packets. Sorry.
Thanks, -Don Skidmore <donald.c.skidm...@intel.com> > -----Original Message----- > From: Fan Du [mailto:fengyuleidian0...@gmail.com] > Sent: Wednesday, January 21, 2015 12:02 AM > To: e1000-devel@lists.sourceforge.net > Subject: [E1000-devel] UDP RSS for fragmented packet > > Hi > > On my testbed/82599EB, a sender generated below packet pattern: > Packet1: { IP fragment1 }{ UDP HDR }{ UDP payload part1 } > Packet2: { IP fragment2 }{ UDP payload part2 } > > Packet1 and Packet2 should assemble into a single user level packet. > The sender can build multiple flows using above packet theme. > On receive side, after turning on UDP RSS, it seems all received packets for > different flows hit on the exactly same queue. > > Just wondering, the NIC is designed to not cover above scenario or I missed > some other configuration? > > IOW, the NIC did assemble Packet1 and Packet2 first and then perform UDP > RSS, if my understanding correct? > > > -- > No zuo no die but I have to try. > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > _______________________________________________ > E1000-devel mailing list > E1000-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/e1000-devel > To learn more about Intel® Ethernet, visit > http://communities.intel.com/community/wired ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
