From: Alan Shieh <ashieh@cs.cornell.edu>
To: linux-net@vger.kernel.org, netdev@vger.kernel.org
Subject: Packet reordering in pcap capture file
Date: Sat, 05 Aug 2006 03:28:38 -0400 [thread overview]
Message-ID: <44D448A6.6020803@cs.cornell.edu> (raw)
Hi everyone,
I sometimes see packets stored out of order in pcap files that generated
by "tcpdump -i any" on kernel 2.4.26 with all packets arriving and
departing on an e1000 NIC. That is, the ordering by receive timestamp on
the packets is not the same as the ordering of the packets within the file.
In my precise scenario, packets of RX packets show up in the log 230 ms
later than they ought to based on the receive timestamp. The kernel
behavior (e.g., the packets that are sent by this node) seems to reflect
the arrival of the Rx packet at the position in the logfile, rather than
the arrival time according to the timestamp.
What are some of the known causes of this behavior? I'd like to know
what locks, etc. might be causing this processing / capture delay.
--
Alan Shieh
PhD Student, Computer Science
331 Upson Hall
Ithaca, NY 14853
next reply other threads:[~2006-08-05 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 7:28 Alan Shieh [this message]
2006-08-05 16:21 ` Packet reordering in pcap capture file Stephen Hemminger
2006-08-07 7:51 ` Alan Shieh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44D448A6.6020803@cs.cornell.edu \
--to=ashieh@cs.cornell.edu \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).