From: "David S. Miller" <dm@neteng.engr.sgi.com>
To: nn@lanta.engr.sgi.com
Cc: torvalds@cs.helsinki.fi, alan@cymru.net,
sparclinux-cvs@caipfs.rutgers.edu, lmlinux@neteng.engr.sgi.com
Subject: Re: linux needs bsd networking stack
Date: Wed, 29 May 1996 15:50:23 -0700 [thread overview]
Message-ID: <199605292250.PAA03268@neteng.engr.sgi.com> (raw)
In-Reply-To: <199605292159.OAA09070@lanta.engr.sgi.com> (nn@lanta)
Date: Wed, 29 May 1996 14:59:58 -0700
From: nn@lanta (Neal Nuckolls)
The "unique" tcp/ip implementation is a liability to linux.
It could also be one of it's greatest assets, and I think this will
turn out to be the case.
Is anyone working to replace the standard linux stack
with port derived from the 4.4BSD code?
I will for now only briefly mention why I think this is not very
desirable.
A couple of weeks ago, Larry was babbling to me "oh the stack is
sloowww, I can't push nearly as much over 100mb/s ether as freebsd
can, etc." I said, "thats peculiar" so I did some investigation and
told Linus about it. Turned out to be a driver bug and after that was
fixed the over the wire numbers are unparalleled.
The Berkeley stack is dead, but it has one redeeming quality which
Linux's stack does desperately need.
It has a well defined architecture, I will agree with lm when he
mentions that it is a jungle of code to sift through in certain
respects. It need a mallet to smooth certain aspects and interfaces
out.
In the end I think it is best to work on hacking the existing (and
upcoming) Linux networking code to have these qualities instead of
stuffing the bsd stack into linux (this has been done before a long
long time ago btw, before linux had any networking, a man by the name
of Charles Hedrick back at Rutgers did it in a few nights).
I think the feeling that the linux stack is "hard to follow" or "has
very little architecture" has a lot to do with the fact that we don't
have 20 books analyzing the code c-statement by c-statement like the
bsd stuff does. If we had that, I think this desire to use the
berkeley stack would not be as strong.
I dislike the berkeley stack, but I am biased in my opinion. I am
biased because of the attitude expressed by the people actively
working on that code set in the free software world these days, I am
also biased because I tend to hack Linux almost exlusively. But, even
barring that I believe that some of the elements of the bsd stack will
end up being completely flawed when plugged into linux, obvious things
like mbufs and other things come to mind right now. It would require
a bit of engineering and greatly upset a large community who has put
their entire heart and soul into the Linux networking code. I believe
at the very least that the Linux networking stack is superior
performance wise without any question, and as everyone knows I have
numbers to prove it ;-)
Later,
David S. Miller
dm@sgi.com
next prev parent reply other threads:[~1996-05-29 22:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-29 21:59 linux needs bsd networking stack Neal Nuckolls
1996-05-29 22:50 ` David S. Miller [this message]
1996-05-30 9:46 ` Alan Cox
1996-05-30 9:46 ` Alan Cox
1996-05-30 5:21 ` Linus Torvalds
1996-05-30 9:43 ` Alan Cox
1996-05-30 9:43 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
1996-05-29 23:04 Larry McVoy
1996-05-30 10:06 ` Alan Cox
1996-05-30 10:06 ` Alan Cox
1996-05-30 0:36 Neal Nuckolls
1996-05-30 3:02 ` David S. Miller
1996-05-30 10:12 ` Alan Cox
1996-05-30 10:12 ` Alan Cox
1996-05-30 18:17 Steve Alexander
1996-05-30 18:17 ` Steve Alexander
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=199605292250.PAA03268@neteng.engr.sgi.com \
--to=dm@neteng.engr.sgi.com \
--cc=alan@cymru.net \
--cc=lmlinux@neteng.engr.sgi.com \
--cc=nn@lanta.engr.sgi.com \
--cc=sparclinux-cvs@caipfs.rutgers.edu \
--cc=torvalds@cs.helsinki.fi \
/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