From: Andi Kleen <ak@suse.de>
To: Doug McNaught <doug@mcnaught.org>
Cc: palbrecht@qwest.net, niv@us.ibm.com,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: question about linux tcp request queue handling
Date: Tue, 8 Jul 2003 01:52:01 +0200 [thread overview]
Message-ID: <20030708015201.4a5ad7e6.ak@suse.de> (raw)
In-Reply-To: <m3brw6rn3m.fsf@varsoon.wireboard.com>
On 07 Jul 2003 18:25:17 -0400
Doug McNaught <doug@mcnaught.org> wrote:
> And furthermore, IIRC, the current Linux networking code is not
> Berkeley-derived, though an earlier version was.
The linux network stack was never BSD derived in any way.
[there are two header files that came from net2, but they do not
contain any code]
-Andi
next prev parent reply other threads:[~2003-07-07 23:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F08858E.8000907@us.ibm.com.suse.lists.linux.kernel>
[not found] ` <001a01c3441c$6fe111a0$6801a8c0@oemcomputer.suse.lists.linux.kernel>
[not found] ` <3F08B7E2.7040208@us.ibm.com.suse.lists.linux.kernel>
[not found] ` <000d01c3444f$e6439600$6801a8c0@oemcomputer.suse.lists.linux.kernel>
[not found] ` <3F090A4F.10004@us.ibm.com.suse.lists.linux.kernel>
[not found] ` <001401c344df$ccbc63c0$6801a8c0@oemcomputer.suse.lists.linux.kernel>
2003-07-07 21:48 ` question about linux tcp request queue handling Andi Kleen
2003-07-07 22:25 ` Doug McNaught
2003-07-07 23:52 ` Andi Kleen [this message]
2003-07-08 0:17 ` Doug McNaught
2003-07-08 0:25 ` Andi Kleen
2003-07-08 14:09 ` Horst von Brand
2003-07-08 4:14 ` Paul Albrecht
2003-07-08 19:23 ` Paul Albrecht
2003-07-06 21:19 Paul Albrecht
-- strict thread matches above, loose matches on Subject: below --
2003-07-06 20:24 Nivedita Singhvi
2003-07-07 0:12 ` Paul Albrecht
2003-07-06 23:59 ` Nivedita Singhvi
2003-07-07 6:20 ` Paul Albrecht
2003-07-07 5:51 ` Nivedita Singhvi
2003-07-07 5:59 ` Nivedita Singhvi
2003-07-07 23:30 ` Paul Albrecht
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=20030708015201.4a5ad7e6.ak@suse.de \
--to=ak@suse.de \
--cc=doug@mcnaught.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.com \
--cc=palbrecht@qwest.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.