From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Michael J Clark <clarkmic@pobox.upenn.edu>
Cc: linux-kernel@vger.kernel.org, rgooch@atnf.csiro.au
Subject: Re: TCP/IP stack
Date: Thu, 28 Jun 2001 23:06:10 +0300 [thread overview]
Message-ID: <20010628230610.K8897@mea-ext.zmailer.org> (raw)
In-Reply-To: <200106281433.f5SEXk800876@pobox.upenn.edu>
In-Reply-To: <200106281433.f5SEXk800876@pobox.upenn.edu>; from clarkmic@pobox.upenn.edu on Thu, Jun 28, 2001 at 10:33:46AM -0400
Richard, should there be (is there?) linux-networking-faq, or can this
be put into the linux-kernel faq ?
On Thu, Jun 28, 2001 at 10:33:46AM -0400, Michael J Clark wrote:
> hey guys,
>
> I have been reading through TCP/IP Illustrated Vol 2 and the linux
> source.
That book describes BSD implementation.
Linux code has been written completely independently, and using
fundamentally different base structure -- instead of PCBs containing
chains of segments, Linux has SKBs with entire segment contiguous
in it.
Function, and structure names are different, naturally.
> Mike
/Matti Aarnio
next prev parent reply other threads:[~2001-06-28 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 14:33 Michael J Clark
2001-06-28 20:06 ` Matti Aarnio [this message]
2001-06-29 15:32 ` Kevin Buhr
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=20010628230610.K8897@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=clarkmic@pobox.upenn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@atnf.csiro.au \
/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
all inboxes | Powered by JetHome®