From: Jeremy Jackson <jerj@coplanar.net>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
netdev@oss.sgi.com,
Linux Knernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: New net features for added performance
Date: Sun, 25 Feb 2001 10:11:50 -0500 [thread overview]
Message-ID: <3A9920B6.393E63B2@coplanar.net> (raw)
In-Reply-To: <3A9842DC.B42ECD7A@mandrakesoft.com> <3A98F417.C38A67BE@uow.edu.au>
Andrew Morton wrote:
(kernel profile of TCP tx/rx)So, naively, the most which can be saved here by
optimising
> the skb and memory usage is 5% of networking load. (1% of
> system load @100 mbps)
>
For a local tx/rx. (open question) What happens with
a router box with netfilter and queueing? Perhaps
this type of optimisation will help more in that case?
think about a box with 4 1G NICs being able to
route AND do QoS per conntrack connection
(ala RSVP and such)
Really what I'm looking for is something like SGI's
STP (Scheduled Transfer Protocol). mmap your
tcp recieve buffer, and have a card smart enough
to figure out header alignment, (i.e. know header
size based on protocol number) transfer only that,
let the kernel process it, then tell the card to DMA
the data from the buffer right into process memory.
(or other NIC)
Make it possible to have the performance of a
Juniper network processor + flexiblity of Linux.
next prev parent reply other threads:[~2001-02-25 15:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-24 23:25 New net features for added performance Jeff Garzik
2001-02-24 23:48 ` Andi Kleen
2001-02-25 0:03 ` Jeff Garzik
2001-02-25 0:12 ` Andi Kleen
2000-01-01 0:19 ` Pavel Machek
2001-03-04 1:19 ` LILO error with 2.4.3-pre1 Steven J. Hill
2001-03-04 1:39 ` Keith Owens
2001-03-04 2:27 ` Tom Sightler
2001-03-04 21:32 ` Mircea Damian
2001-03-04 23:05 ` Guest section DW
2001-03-04 2:39 ` Andre Tomt
2001-03-04 3:32 ` Steven J. Hill
2001-03-04 13:35 ` Alan Cox
2001-02-25 0:13 ` New net features for added performance Jeff Garzik
2001-02-25 0:16 ` Andi Kleen
2001-02-25 11:49 ` Rusty Russell
2001-02-26 23:48 ` David S. Miller
2001-02-27 0:03 ` Andi Kleen
2001-02-27 0:08 ` David S. Miller
2001-02-27 2:53 ` Jeremy Jackson
2001-02-27 19:59 ` kuznet
2001-02-25 1:55 ` Michael Richardson
2001-02-25 2:32 ` Jeremy Jackson
2001-02-25 3:23 ` Chris Wedgwood
2001-02-25 12:41 ` Werner Almesberger
2001-02-25 13:57 ` Chris Wedgwood
2001-02-25 2:38 ` Noah Romer
2001-03-03 23:32 ` Jes Sorensen
2001-02-25 12:01 ` Andrew Morton
2001-02-25 15:11 ` Jeremy Jackson [this message]
2001-02-25 12:22 ` Werner Almesberger
2001-03-12 15:08 ` Jes Sorensen
2001-02-25 13:08 ` Jonathan Morton
2001-02-26 23:46 ` David S. Miller
2001-02-27 0:07 ` Jeff Garzik
2001-02-27 0:10 ` David S. Miller
2001-03-01 21:06 ` Jes Sorensen
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=3A9920B6.393E63B2@coplanar.net \
--to=jerj@coplanar.net \
--cc=andrewm@uow.edu.au \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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