From: Roland Dreier <roland@topspin.com>
To: ZI ZHOU <zhouzi@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HELP ! Why my dev->hard_start_xmit get called three times for one ping packet?
Date: 14 Apr 2004 19:15:29 -0700 [thread overview]
Message-ID: <52oepu7zr2.fsf@topspin.com> (raw)
In-Reply-To: <20040415012536.61202.qmail@web12505.mail.yahoo.com>
ZI> After I configure the ethernet interface(it's a PCI card
ZI> plugged in my debian PC), I run command ' ping -c 1
ZI> 192.168.0.100', (the interface is configured with IP address
ZI> 192.168.0.35), I used smartbit to look at the wire and found 3
ZI> ping packets. From the debugging info, I can see
ZI> dev->hard_start_xmit is called three times, the DMA engine
ZI> seems to be acting correctly, and each time hard_start_xmit is
ZI> invoked the skb address is different. How can this happen?
Are any of the 3 packets actually arp packets?
- Roland
next prev parent reply other threads:[~2004-04-15 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 1:25 HELP ! Why my dev->hard_start_xmit get called three times for one ping packet? ZI ZHOU
2004-04-15 2:15 ` Roland Dreier [this message]
2004-04-15 17:22 ` ZI ZHOU
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=52oepu7zr2.fsf@topspin.com \
--to=roland@topspin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zhouzi@yahoo.com \
/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