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 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  5:21 ` Linus Torvalds
  1996-05-30  9:43 ` Alan Cox
  2 siblings, 1 reply; 16+ messages in thread
From: David S. Miller @ 1996-05-29 22:50 UTC (permalink / raw)
  To: nn; +Cc: torvalds, alan, sparclinux-cvs, lmlinux

   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

^ 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  0:36 Neal Nuckolls
@ 1996-05-30  3:02 ` David S. Miller
  1996-05-30 10:12 ` Alan Cox
  1 sibling, 0 replies; 16+ messages in thread
From: David S. Miller @ 1996-05-30  3:02 UTC (permalink / raw)
  To: nn; +Cc: lmlinux, sparclinux-cvs, alan, torvalds

   Date: Wed, 29 May 1996 17:36:19 -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.

   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, whats funny is that this is exactly what the people doing
work on the linux stack have in fact done.  Check out the ideas people
have put into various berkeley based ventures and research, place our
own implementation of the idea into the linux stack, and then improve
upon it.  The idea behind publicly available standards (at least I
believe) was to promote no single entity to have this "defacto" thing
which controlled the protocol or what have you, the berkeley
phenomenon is not encouraging this idea and is in fact against it.
Here the berkeley interpretation and implementation is being
considered "the" interpretation and "the" implementation.  The Linux
code in general moves at an advanced rate, it is constantly evolving
and changing for the purposes of improvement.  One could argue that
this is what makes it so hard to pin down and become very acquainted
with it and not just the fact that it's objects and interfaces are not
as well defined (as lm mentions, of which I whole heartedly agree, I
would some day like to see the Linux networking be as intuitive and
seamless as the vm/mm Linux layers, Linus has mentioned moves in this
direction via fully integrating the socks more completely into the
inode among other things).

   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.

I wish it wouldn't come down to a discussion about "what license is
better for who and why", I'd rather this be about technical merit.
But, I am beginning to realize that this may not be possible.  I want
Linux to strive and always be on the bleeding edge, as it has been,
personally I believe that the "GPL kiss of death" is what makes that
possible and will guarentee that this capability cannot be taken
away.

   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?

You are correct, this is what "free software" (there is a distinction)
is all about.  However what it is not about, and what could kill free
software is if the "BSD kiss of death" allowed someone to make
significant improvements to the Linux code and due to the berkeley
license allowed that entity to keep those improvements to themselves
so that the free software community loses out.  This is precisely what
the GPL tries to avoid...  Very frequently, Linus himself mentions
that the GPL is what has made Linux as powerful as it now is, and he
also frequently mentions that GPL'ing the Linux code is the best
decision he has ever made.  I tend to agree with him.

But like I said, I'd rather such a decision be made based upon a
technical decision not a "who has the viable licensing terms"
decision.

It was mentioned that you are more familiar with the berkeley code and
many people are.  I am more familiar with the Linux code and the
work/research which has gone into it, do I have an argument as well?
I would not present it this way or drive an argument in that fashion I
think.  There exists a significant group of people who are in my
position and as well there are many in the position you speak of.
However, I have been making a significant effort over the past year or
so to become familiar with the berkeley code so that I possess the
ability to tackle decisions like this based on technical merit, and
not turn it into a GPL vs. BSD discussion.  Are people supportive of
the berkeley side of this argument willing to do the same?  I know a
few such as lm etc., I would not say they exist within the majority
though.

Later,
David S. Miller
dm@sgi.com

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

* Re: linux needs bsd networking stack
  1996-05-29 21:59 linux needs bsd networking stack Neal Nuckolls
  1996-05-29 22:50 ` David S. Miller
@ 1996-05-30  5:21 ` Linus Torvalds
  1996-05-30  9:43 ` Alan Cox
  2 siblings, 0 replies; 16+ messages in thread
From: Linus Torvalds @ 1996-05-30  5:21 UTC (permalink / raw)
  To: Neal Nuckolls; +Cc: alan, sparclinux-cvs, lmlinux



On Wed, 29 May 1996, Neal Nuckolls wrote:
> 
> 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?

Simple answer: it won't happen.

The _only_ advantage of the BSD stack is the de-facto standard thing, and 
quite frankly that one doesn't make much of a difference - Linux _will_ 
be the facto standard in one or two more years if everything goes right. 
Trying to port the BSD stack would be a major mistake, imho.

I used to think the BSD stack was an option that we might want to take some
day, but I don't think so any more. My main concerns were performance and
compatibility, and we've got them both. The problems we still have in
networking are not worth worrying about in this context - we'd have a lot
more problems if we tried to switch and they wouldn't be any easier to solve. 

Note that this doesn't mean we shouldn't look at parts of the BSD stack 
for interesting things (and the BSD stack has obviously been there as a 
reference). But a whole-sale BSD stack port is not going to happen.

		Linus

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

* Re: linux needs bsd networking stack
  1996-05-29 21:59 linux needs bsd networking stack Neal Nuckolls
  1996-05-29 22:50 ` David S. Miller
  1996-05-30  5:21 ` Linus Torvalds
@ 1996-05-30  9:43 ` Alan Cox
  1996-05-30  9:43   ` Alan Cox
  2 siblings, 1 reply; 16+ messages in thread
From: Alan Cox @ 1996-05-30  9:43 UTC (permalink / raw)
  To: Neal Nuckolls; +Cc: torvalds, alan, sparclinux-cvs, lmlinux

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

So we should use a defacto BSD stack because its a defacto stack. Ok there is this
great OS called windows3. See you later

> The "unique" tcp/ip implementation is a liability to linux.

I'm not convinced it is. A whole load of SGI people (LM notably) seem intent on "BSD
stack, BSD stack, BSD stack". Everyone else I hear is saying "How fast can it go",
"How stable can we make it", "Will you please make sure its as solid in 2.0 as in 1.2"

> Is anyone working to replace the standard linux stack
> with port derived from the 4.4BSD code?

No -

o	The BSD stack doesnt do IPX, AX25, NetROM, Appletalk
o	There will be no defacto IPv6 for BSD, there are several species
o	The licensing doesnt permit the two to meet easily
o	You can't do 400Mbits/second with mbufs so you'd have to break the BSD code
	anyway

Im not convinced about the rest of the argument either. I know one big vendor using
the BSD stack for a project. I know several using Linux (Things like the firewall
from Mazama). We are seeing primary rate ISDN support for Linux starting to appear,
and already have the heavy provider end multiple serial cards.

For routers, anyone using a PC style architecture is bounding themselves to small
routers anyway. No matter how good the code is you will soon need fancy hardware to
handle BGP4, 50,000 routes and fast 100baseT speed switching. And there is no
defacto BSD IPv6

Alan

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

* Re: linux needs bsd networking stack
  1996-05-30  9:43 ` Alan Cox
@ 1996-05-30  9:43   ` Alan Cox
  0 siblings, 0 replies; 16+ messages in thread
From: Alan Cox @ 1996-05-30  9:43 UTC (permalink / raw)
  To: Neal Nuckolls; +Cc: torvalds, alan, sparclinux-cvs, lmlinux

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

So we should use a defacto BSD stack because its a defacto stack. Ok there is this
great OS called windows3. See you later

> The "unique" tcp/ip implementation is a liability to linux.

I'm not convinced it is. A whole load of SGI people (LM notably) seem intent on "BSD
stack, BSD stack, BSD stack". Everyone else I hear is saying "How fast can it go",
"How stable can we make it", "Will you please make sure its as solid in 2.0 as in 1.2"

> Is anyone working to replace the standard linux stack
> with port derived from the 4.4BSD code?

No -

o	The BSD stack doesnt do IPX, AX25, NetROM, Appletalk
o	There will be no defacto IPv6 for BSD, there are several species
o	The licensing doesnt permit the two to meet easily
o	You can't do 400Mbits/second with mbufs so you'd have to break the BSD code
	anyway

Im not convinced about the rest of the argument either. I know one big vendor using
the BSD stack for a project. I know several using Linux (Things like the firewall
from Mazama). We are seeing primary rate ISDN support for Linux starting to appear,
and already have the heavy provider end multiple serial cards.

For routers, anyone using a PC style architecture is bounding themselves to small
routers anyway. No matter how good the code is you will soon need fancy hardware to
handle BGP4, 50,000 routes and fast 100baseT speed switching. And there is no
defacto BSD IPv6

Alan

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

* Re: linux needs bsd networking stack
  1996-05-29 22:50 ` David S. Miller
@ 1996-05-30  9:46   ` Alan Cox
  1996-05-30  9:46     ` Alan Cox
  0 siblings, 1 reply; 16+ messages in thread
From: Alan Cox @ 1996-05-30  9:46 UTC (permalink / raw)
  To: David S. Miller; +Cc: nn, torvalds, alan, sparclinux-cvs, lmlinux

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

I hope to be working full time on this eventually (like when people are paying me
for it). I've also started documentation at the driver and skbuff level and will
work over it bit by bit - see forthcoming Linux Journal articles then going into the
KHG.

> 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 ;-)

Before you admire the performance numbers get the pre2.1 code off Pedro Roque. Now he
has added really neat header prediction code it kicks pre2.0's butt even though its
doing a surplus memory alloc we need to tidy up

Alan

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

* Re: linux needs bsd networking stack
  1996-05-30  9:46   ` Alan Cox
@ 1996-05-30  9:46     ` Alan Cox
  0 siblings, 0 replies; 16+ messages in thread
From: Alan Cox @ 1996-05-30  9:46 UTC (permalink / raw)
  To: David S. Miller; +Cc: nn, torvalds, alan, sparclinux-cvs, lmlinux

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

I hope to be working full time on this eventually (like when people are paying me
for it). I've also started documentation at the driver and skbuff level and will
work over it bit by bit - see forthcoming Linux Journal articles then going into the
KHG.

> 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 ;-)

Before you admire the performance numbers get the pre2.1 code off Pedro Roque. Now he
has added really neat header prediction code it kicks pre2.0's butt even though its
doing a surplus memory alloc we need to tidy up

Alan

^ 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
  1996-05-30 10:06   ` Alan Cox
  0 siblings, 1 reply; 16+ messages in thread
From: Alan Cox @ 1996-05-30 10:06 UTC (permalink / raw)
  To: Larry McVoy; +Cc: dm, nn, torvalds, alan, sparclinux-cvs, lmlinux

> 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

We have these.

> 	interface structure for different media types

We have these

> 	socket structure that cleanly handles different protocols

We have most of this.

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

Yep. For 2.0 we have all the core stuff. For pre 2.1 we have stuff going beyond
what BSD is doing - Vegas flow control. If you want to work on stealing and working
stuff in talk with Pedro Roque, get pre 2.1 and take a good look.

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

We could certainly add the allocate via device at very little cost. We just start
using dev->kmalloc(). Note that you can't always win on this a packet may change
route.

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

The Linux one is semi designed for MP work. A given socket can do its own locking,
and there are only a small number of areas of overlap at the moment. Notably

Demultiplex table needs locks
Multiple processor writes in parallel/reads in parallel on datagram requires about
	10 lines of lock code.
We dont run the net_bh() in parallel although most of it we can do very easily.

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

That certainly cant be counter-productive.

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

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.

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

So long as it still runs very fast for the 99.99% of people with a single CPU 486 PC.
Thats the primary target by market volume.

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

Its coming. In fact AW should now have released an English language version of the
1.2 kernel programming book. 

Alan

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

* Re: linux needs bsd networking stack
  1996-05-30 10:06 ` Alan Cox
@ 1996-05-30 10:06   ` Alan Cox
  0 siblings, 0 replies; 16+ messages in thread
From: Alan Cox @ 1996-05-30 10:06 UTC (permalink / raw)
  To: Larry McVoy; +Cc: dm, nn, torvalds, alan, sparclinux-cvs, lmlinux

> 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

We have these.

> 	interface structure for different media types

We have these

> 	socket structure that cleanly handles different protocols

We have most of this.

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

Yep. For 2.0 we have all the core stuff. For pre 2.1 we have stuff going beyond
what BSD is doing - Vegas flow control. If you want to work on stealing and working
stuff in talk with Pedro Roque, get pre 2.1 and take a good look.

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

We could certainly add the allocate via device at very little cost. We just start
using dev->kmalloc(). Note that you can't always win on this a packet may change
route.

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

The Linux one is semi designed for MP work. A given socket can do its own locking,
and there are only a small number of areas of overlap at the moment. Notably

Demultiplex table needs locks
Multiple processor writes in parallel/reads in parallel on datagram requires about
	10 lines of lock code.
We dont run the net_bh() in parallel although most of it we can do very easily.

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

That certainly cant be counter-productive.

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

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.

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

So long as it still runs very fast for the 99.99% of people with a single CPU 486 PC.
Thats the primary target by market volume.

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

Its coming. In fact AW should now have released an English language version of the
1.2 kernel programming book. 

Alan

^ 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
  1996-05-30 10:12   ` Alan Cox
  1 sibling, 1 reply; 16+ messages in thread
From: Alan Cox @ 1996-05-30 10:12 UTC (permalink / raw)
  To: Neal Nuckolls; +Cc: dm, lmlinux, sparclinux-cvs, alan, torvalds

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

Chuckle. The BSD stack doesn't even match the RFC's [ie THE STANDARD]

> 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

Let me see: Routing protocols is userspace. ATM signalling we have (going in
2.1), Vegas we have in the pre 2.1 stuff. realtime - if you mean low latency
then take a look at unet.

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

So "We should change it for the startups" was message 1. "The startups wont
use it was message two". Do you have bullet holes in your shoes by any
chance ?

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

We can't use the 4.4BSD stack so that issue is moot. Free software is also about high
technical quality. If I wanted to get paid lots of money for hacking kernels I'd go
and work for mirkosoft

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

* Re: linux needs bsd networking stack
  1996-05-30 10:12 ` Alan Cox
@ 1996-05-30 10:12   ` Alan Cox
  0 siblings, 0 replies; 16+ messages in thread
From: Alan Cox @ 1996-05-30 10:12 UTC (permalink / raw)
  To: Neal Nuckolls; +Cc: dm, lmlinux, sparclinux-cvs, alan, torvalds

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

Chuckle. The BSD stack doesn't even match the RFC's [ie THE STANDARD]

> 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

Let me see: Routing protocols is userspace. ATM signalling we have (going in
2.1), Vegas we have in the pre 2.1 stuff. realtime - if you mean low latency
then take a look at unet.

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

So "We should change it for the startups" was message 1. "The startups wont
use it was message two". Do you have bullet holes in your shoes by any
chance ?

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

We can't use the 4.4BSD stack so that issue is moot. Free software is also about high
technical quality. If I wanted to get paid lots of money for hacking kernels I'd go
and work for mirkosoft

^ 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

* Re: linux needs bsd networking stack
  1996-05-30 18:17 Steve Alexander
@ 1996-05-30 18:17 ` Steve Alexander
  0 siblings, 0 replies; 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