From: J Sloan <jjs@toyota.com>
To: Mårten Wikström <Marten.Wikstrom@framfab.se>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: How to optimize routing performance
Date: Thu, 15 Mar 2001 10:09:39 -0800 [thread overview]
Message-ID: <3AB10563.42FE7170@toyota.com> (raw)
In-Reply-To: <E6D22E487D45D411931B00508BCF93E75C0326@storeg001.framfab.se>
Just my .02 -
There are some scheduler patches that are not part of the
main kernel tree at this point (mostly since they have yet to
be optimized for the common case) which make quite a big
difference under heavy load - you might want to check out:
http://lse.sourceforge.net/scheduling/
cu
Jup
Mårten Wikström wrote:
> I've performed a test on the routing capacity of a Linux 2.4.2 box versus a
> FreeBSD 4.2 box. I used two Pentium Pro 200Mhz computers with 64Mb memory,
> and two DEC 100Mbit ethernet cards. I used a Smartbits test-tool to measure
> the packet throughput and the packet size was set to 64 bytes. Linux dropped
> no packets up to about 27000 packets/s, but then it started to drop packets
> at higher rates. Worse yet, the output rate actually decreased, so at the
> input rate of 40000 packets/s almost no packets got through. The behaviour
> of FreeBSD was different, it showed a steadily increased output rate up to
> about 70000 packets/s before the output rate decreased. (Then the output
> rate was apprx. 40000 packets/s).
> I have not made any special optimizations, aside from not having any
> background processes running.
>
> So, my question is: are these figures true, or is it possible to optimize
> the kernel somehow? The only changes I have made to the kernel config was to
> disable advanced routing.
>
> Thanks,
>
> Mårten
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-03-15 18:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 7:23 How to optimize routing performance Mårten Wikström
2001-03-15 12:32 ` Rik van Riel
2001-03-15 16:20 ` Martin Josefsson
2001-03-15 18:09 ` J Sloan [this message]
2001-03-16 2:05 ` Rik van Riel
2001-03-15 19:17 ` J Sloan
2001-03-15 19:36 ` Gregory Maxwell
2001-03-15 19:45 ` J Sloan
2001-03-15 19:44 ` Mike Kravetz
2001-03-16 2:35 ` Rik van Riel
2001-03-15 19:28 ` J Sloan
-- strict thread matches above, loose matches on Subject: below --
2001-03-15 14:19 Robert Olsson
2001-03-16 0:38 ` Rik van Riel
2001-03-15 18:45 ` Robert Olsson
2001-03-15 19:30 ` Jonathan Morton
2001-03-15 19:54 ` Robert Olsson
2001-03-15 21:01 ` jamal
2001-03-15 20:16 Jonathan Earle
[not found] <3AB12640.79E7B4FB@colorfullife.com>
2001-03-15 21:39 ` Robert Olsson
2001-03-16 7:21 Mårten Wikström
2001-03-16 8:08 ` Martin Josefsson
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=3AB10563.42FE7170@toyota.com \
--to=jjs@toyota.com \
--cc=Marten.Wikstrom@framfab.se \
--cc=linux-kernel@vger.kernel.org \
/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