From: cranium 2003 <cranium.2003@gmail.com>
To: netdev@oss.sgi.com, kernelnewbies <kernelnewbies@nl.linux.org>
Subject: Which function at link layer sends packet?
Date: Thu, 3 Feb 2005 18:48:19 +0530 [thread overview]
Message-ID: <1d55641b05020305182d423c57@mail.gmail.com> (raw)
Hello,
In a LAN i have 2 pcs host1 with 10.0.2.10 and host2 with
eth0:10.0.0.100 and eth1:192.168.1.1 Both are connected to switch.
what i observe that when i ping from 10.0.2.10 to 192.168.1.1 then
packet is sent through dev_queue_xmit_nit. In that function it goes
upto ptype->func(skb2, skb->dev, ptype);
and then i am not getting which functions get called but then i found
call goes to ethernet driver to NIC card. Does that mean above
statement calls hard_start_xmit?
Then i reboot my linux RH9 with 2.4.24 kernel PC and again ping
to 192.168.1.1 and found that packet transmission is not going
through dev_queu_xmit_nit but from dev_queue_xmit to hard_start_xmit.
regards,
cranium.
reply other threads:[~2005-02-03 13:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1d55641b05020305182d423c57@mail.gmail.com \
--to=cranium.2003@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).