All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@cymru.net>
To: dm@neteng.engr.sgi.com (David S. Miller)
Cc: nn@lanta.engr.sgi.com, 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: Thu, 30 May 1996 10:46:46 +0100 (BST)	[thread overview]
Message-ID: <199605300946.KAA24198@snowcrash.cymru.net> (raw)
In-Reply-To: <199605292250.PAA03268@neteng.engr.sgi.com> from "David S. Miller" at May 29, 96 03:50:23 pm

> 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

WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@cymru.net>
To: "David S. Miller" <dm@neteng.engr.sgi.com>
Cc: nn@lanta.engr.sgi.com, 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: Thu, 30 May 1996 10:46:46 +0100 (BST)	[thread overview]
Message-ID: <199605300946.KAA24198@snowcrash.cymru.net> (raw)
Message-ID: <19960530094646.Z5dhAoPc3S1VRLZFpB5X2eQtja-Jr1c3mB2Wb2-LJyI@z> (raw)
In-Reply-To: <199605292250.PAA03268@neteng.engr.sgi.com> from "David S. Miller" at May 29, 96 03:50:23 pm

> 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

  reply	other threads:[~1996-05-30  9: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
1996-05-30  9:46   ` Alan Cox [this message]
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
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=199605300946.KAA24198@snowcrash.cymru.net \
    --to=alan@cymru.net \
    --cc=dm@neteng.engr.sgi.com \
    --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 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.