I have seeing some very strange behavior with our e1000e driver.  We are trying 
to use this interface to capture high rate network data and store it to disk.  
However, we seem to be dropping the very first packet we get on each socket we 
create.

It almost appears that the very first multicast datagram from any given source 
is missing (our application listens on multiple ports to any sources of data; 
anyone can send to these ports data that needs to be logged and the application 
will log it; I seem to miss the first packet from each source).  Is that 
expected behavior?

Our data are all UDP multicast datagrams on a local subnet, so we don't have to 
worry about a message getting lost in routing or anything else.  What is 
bothering me is that ifconfig does not report any errors or dropped packets, 
neither does ethtool.

# ethtool -i eth0
driver: e1000e
version: 1.3.10-k2
firmware-version: 1.8-4
bus-info: 0000:00:19.0

I know that the datagrams on the wire from the source - I have verified that 
with Wireshark.  However, my application code just never picks it up.  Once I 
get past these first missing packets, I do not miss another packet - even at 
our 40 MB/s rates.

Am I configuring my socket incorrectly?  I can provide code if someone thinks 
that may be an issue.  Could there be a bug in the driver?  I can't see how 
that would be since I get every single packet after these first ones.  I am 
baffled at this!

Thanks,

Jonathan


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
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