Netdev List
 help / color / mirror / Atom feed
From: "'Jeff' R. Steinhagen" <Jeff@steinhagen.ch>
To: netdev@oss.sgi.com
Subject: forcing a packet to go through hw net device
Date: Mon, 09 May 2005 14:58:42 +0200	[thread overview]
Message-ID: <200505091458.42118.Jeff@steinhagen.ch> (raw)

Hi!

I have a (maybe trivial) question about the kernel's networking code:

A packet with an "outside" destination goes through all layers including the 
hardware interface (user->socket->protocol->IP->HW). However if the packet is 
addressed to a local IP the transport through and checks by the hardware 
layer are avoided. This is perfectly OK for "normal" network usage.

I am profiling some network hardware and related code. Is it possible to force 
an internally generated packet to be send through all/the hardware layers?

Thanks for your help!

Cheers,
Jeff

             reply	other threads:[~2005-05-09 12:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 12:58 'Jeff' R. Steinhagen [this message]
2005-05-10  6:02 ` forcing a packet to go through hw net device Sumit
2005-05-10  6:21   ` 'Jeff' R. Steinhagen

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=200505091458.42118.Jeff@steinhagen.ch \
    --to=jeff@steinhagen.ch \
    --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