linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Cecil <dcecil@oz.agile.tv>
To: linux-kernel@vger.kernel.org
Subject: Tracing a network device
Date: Tue, 15 May 2001 19:03:57 +1000	[thread overview]
Message-ID: <3B00F0FD.2060905@oz.agile.tv> (raw)

Guys,

I'm working on a network device that will forward some packets before 
they get to netif_rx and thus net_rx_action.  Thus, the forwarded 
packets handled by my device/protocol would not be traced by the 
existing trace utility (AF_PACKET etc.), correct?  Am I correct in 
assuming that there is no existing way to trace such fast-forwarded packets?

Mmy proposed solution to the problem is to implement a socket type for 
my (new) protocol family that will allow such packets to be traced.  
Simply open a socket eg socket(AF_MINE, SOCK_RAW, MYPROTO_TRACE) and you 
get a copy of the packets from the driver.  Is this an acceptable 
solution or are people cringing at the thought?

I came across the ethertap driver and it seems to do something along the 
lines of what I want to do, but I need to look at it more closely.

Comments?

Thanks,
Dave


                 reply	other threads:[~2001-05-15  8:59 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=3B00F0FD.2060905@oz.agile.tv \
    --to=dcecil@oz.agile.tv \
    --cc=linux-kernel@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).