From: Eli Carter <eli.carter@inet.com>
To: linux-kernel@vger.kernel.org
Subject: question: ip_rcv(), dst_entry (2.2)
Date: Thu, 16 Aug 2001 17:14:22 -0500 [thread overview]
Message-ID: <3B7C45BE.3828D2CB@inet.com> (raw)
Greetings,
I've been studying the 2.2 networking code and, well, I'm beginning to
feel overwhelmed...
I think I (mostly) understand the network driver part of it, but I'm
getting lost in the dst_entry area, I think from both directions...
I didn't find a whole lot on google or linux/Documentation .
Does anyone have pointers to information to guide me through the 2.2
networking code? (Or even volunteers to give me an idea of what I'm
looking at and how it works?) I'm particularly interested in
information on the API boundaries in the 2.2.x network code.
TIA,
Eli
--------------------. Real Users find the one combination of bizarre
Eli Carter \ input values that shuts down the system for days.
eli.carter(a)inet.com `-------------------------------------------------
next reply other threads:[~2001-08-16 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 22:14 Eli Carter [this message]
2001-08-17 20:03 ` question: ip_rcv(), dst_entry (2.2) Eli Carter
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=3B7C45BE.3828D2CB@inet.com \
--to=eli.carter@inet.com \
--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