Linux MIPS Architecture development
 help / color / mirror / Atom feed
* linux needs bsd networking stack
@ 1996-05-29 21:59 Neal Nuckolls
  1996-05-29 22:50 ` David S. Miller
                   ` (2 more replies)
  0 siblings, 3 replies; 16+ messages in thread
From: Neal Nuckolls @ 1996-05-29 21:59 UTC (permalink / raw)
  To: torvalds, alan; +Cc: sparclinux-cvs, lmlinux


Silicon Valley is bubbling with networking startups.
Many of these new small companies are designing products
based on PC motherboards and doing some sw and/or hw
customization to turn them into networking switches,
routers, firewalls, etc.  Rather than embedding a RTOS,
they are choosing a free unix and usually this is FreeBSD
since Linux networking is not the de facto BSD stack.
The "unique" tcp/ip implementation is a liability to linux.
Is anyone working to replace the standard linux stack
with port derived from the 4.4BSD code?

thanks.

neal nuckolls
nn@engr.sgi.com

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: linux needs bsd networking stack
@ 1996-05-29 23:04 Larry McVoy
  1996-05-30 10:06 ` Alan Cox
  0 siblings, 1 reply; 16+ messages in thread
From: Larry McVoy @ 1996-05-29 23:04 UTC (permalink / raw)
  To: dm; +Cc: nn, torvalds, alan, sparclinux-cvs, lmlinux

:    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?
: 
: 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.

That's not quite true, I think the BSD numbers are still better, I'll
have full lmbench apples to apples runs on the same hardware at the 
end of this week.

: It [bsd] 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.  

This is one of my complaints.  The BSD stack has a defined set of "objects"
for dealing with networking; an incomplete list:

	protocol structure for different address families
	interface structure for different media types
	socket structure that cleanly handles different protocols

Another big plus of the BSD stack is tcp_input.c and tcp_output.c.  These
are what most people mean when they say "BSD networking".

Downsides of BSD:

	. I don't particlularly like mbufs; I agree with Linus & Alan that
	they are overkill.  

	. There are layering "invariants" that affect performance: you really
	should allocate your send buffers from the interface driver, because
	it could do some interesting things that would minimize cache flushing.
	I think Van's prototype did this for witless cards.

	. Single processor design.  This is the biggest drawback, IMO.

Proposal/suggestion:

	. Come up with a strawman proposal for the set of "objects" we think
	  we need in Linux.  Do this as part of the work Linus suggested to
	  merge the socket ops with the vfs ops.

	. Steal the TCP code outright.  Nuke the mbuf stuff, use the skbufs
	  or a slightly modified version thereof.

	. Design in SMP support from the start.  This means thinking about
	  thousands of connections running in parallel.

: 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.

Yeah, but a very reasonable point is "we don't have that".  BSD does.
This is a big deal.  Documentation is useful.

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: linux needs bsd networking stack
@ 1996-05-30  0:36 Neal Nuckolls
  1996-05-30  3:02 ` David S. Miller
  1996-05-30 10:12 ` Alan Cox
  0 siblings, 2 replies; 16+ messages in thread
From: Neal Nuckolls @ 1996-05-30  0:36 UTC (permalink / raw)
  To: dm; +Cc: lmlinux, sparclinux-cvs, alan, torvalds


>> 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.

Whether the linux kernel networking implementation is better or
worse than the BSD code isn't my point. The fact that it's not
clearly superior, only very different, from the standard is.

Most unix and internet R&D community protocol development has
been and continues to be within a BSD environment which means that
BSD-based kernel networking code is prevalent. If I'm doing some
work in this area I can readily grab many free BSD-based protocol
pieceparts off the net. New routing protocols, ATM signalling, TCP
conjestion improvements, realtime protocol stacks, etc. are all
developed in a BSD kernel networking environment.  Have been for
years. That's not likely to change. There are hundreds of people
out there that really know BSD networking. This availability of
people and code makes it the standard.

Actually, for the startups that I mentioned - those interested in
shipping a commercial product - there is no choice, it's FreeBSD,
because it comes without the GPL kiss of death.

> 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

I think that basing any improvements on a 4.4BSD-based linux stack
would result in something more usable.  Also, as a side effect, it
would encourage more talented networking people to participate and
isn't this what freeware is all about?

neal

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: linux needs bsd networking stack
@ 1996-05-30 18:17 Steve Alexander
  1996-05-30 18:17 ` Steve Alexander
  0 siblings, 1 reply; 16+ messages in thread
From: Steve Alexander @ 1996-05-30 18:17 UTC (permalink / raw)
  To: Alan Cox; +Cc: Larry McVoy, dm, nn, torvalds, sparclinux-cvs, lmlinux

Alan Cox <alan@cymru.net> writes:
>We can't steal it outright. 4.4BSD has abominable problems as is. The FreeBSD 
>people
>have the worst of them fixed but don't have stuff like Vegas and have all the 
>horrible spoofing problems caused by bad timers.

I'm not sure I understand what that means, but I'm pretty sure that Vegas is
not universally agreed to be a good idea, unless I've missed a meeting.

Just to set the record straight, there are people at SGI who don't like either
the BSD or Linux stacks ;->.

The one thing that I will say about the Linux stack is that it is evolving much
more rapidly than any of the public BSD versions are (I spent some time porting
aliases forward from one version to another for a friend, and the improvements
between versions were amazing), so at some point it will probably win on
functionality.

-- Steve

^ permalink raw reply	[flat|nested] 16+ messages in thread

end of thread, other threads:[~1996-05-30 18:21 UTC | newest]

Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1996-05-29 21:59 linux needs bsd networking stack Neal Nuckolls
1996-05-29 22:50 ` David S. Miller
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox