From: linux lover <linux.lover2004@gmail.com>
To: linux-net@vger.kernel.org
Cc: netdev@oss.sgi.com
Subject: what is use of dev_queue_xmit_nit?
Date: Tue, 21 Dec 2004 15:36:14 +0530 [thread overview]
Message-ID: <72c6e379041221020653e7a488@mail.gmail.com> (raw)
Hello all,
I want to know what is use of dev_queue_xmit_nit function in
dev.c file? Also why it calls following statement
ptype->func(skb2, skb->dev, ptype);
Also why skb2 is created by cloning skb? Acually i trace TCP packets
and found that control goes from neigh_resolve_output to directly
dev_queue_xmit_nit and then to HW driver 8139too.c? I want to know why
it not goes from dev_queue_xmit? I place printk statments and found
after dev_queue_xmit_nit control moves to network interface driver?
Help to understand the control packet path.
Thanks in advance.
linux_lover
next reply other threads:[~2004-12-21 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 10:06 linux lover [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-23 16:50 what is use of dev_queue_xmit_nit? linux lover
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=72c6e379041221020653e7a488@mail.gmail.com \
--to=linux.lover2004@gmail.com \
--cc=linux-net@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.