From: "David S. Miller" <davem@redhat.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: mcr@sandelman.ottawa.on.ca, netdev@oss.sgi.com
Subject: Re: Best way to hook incoming eth pkts?
Date: Wed, 20 Aug 2003 10:54:37 -0700 [thread overview]
Message-ID: <20030820105437.73dc86db.davem@redhat.com> (raw)
In-Reply-To: <20030820175929.GD23984@gtf.org>
On Wed, 20 Aug 2003 13:59:29 -0400
Jeff Garzik <jgarzik@pobox.com> wrote:
> On Wed, Aug 20, 2003 at 01:49:28PM -0400, Michael Richardson wrote:
> > For ethernet protocols, you can just register the protocol handler, and you
> > will get them.
>
> Dumb question: how? example code, or relevant functions to grep for?
He's talking about net/core/dev.c:dev_add_pack()
next prev parent reply other threads:[~2003-08-20 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 15:47 Best way to hook incoming eth pkts? Jeff Garzik
2003-08-20 17:48 ` Bryan O'Sullivan
2003-08-20 17:51 ` Jeff Garzik
2003-08-20 17:49 ` Michael Richardson
2003-08-20 17:59 ` Jeff Garzik
2003-08-20 17:54 ` David S. Miller [this message]
2003-08-20 18:15 ` Jeff Garzik
2003-08-20 18:17 ` David S. Miller
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=20030820105437.73dc86db.davem@redhat.com \
--to=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=mcr@sandelman.ottawa.on.ca \
--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).