From: "Bryan O'Sullivan" <bos@serpentine.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: netdev@oss.sgi.com
Subject: Re: Best way to hook incoming eth pkts?
Date: 20 Aug 2003 10:48:17 -0700 [thread overview]
Message-ID: <1061401697.12293.8.camel@serpentine.internal.keyresearch.com> (raw)
In-Reply-To: <20030820154727.GB9119@gtf.org>
On Wed, 2003-08-20 at 08:47, Jeff Garzik wrote:
> ATA-over-ethernet has its own
> IANA-registered ethernet type, but netconsole and netdump are using
> IP/UDP instead of a custom ethernet protocol.
This is useful, because it minimises the work needed to get them going
over other transports, such as Myrinet. I'd rather not see the UDP
encapsulation go away. Netconsole is already messy enough to configure
and deal with; Matt Mackall's 2.6 forward port, that makes configuration
more IP-oriented instead of less, is a step in the right direction.
<b
next prev parent reply other threads:[~2003-08-20 17:48 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 [this message]
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
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=1061401697.12293.8.camel@serpentine.internal.keyresearch.com \
--to=bos@serpentine.com \
--cc=jgarzik@pobox.com \
--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).