From: Gregory Maxwell <greg@linuxpower.cx>
To: Nye Liu <nyet@curtis.curtisfong.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Very high bandwith packet based interface and performance problems
Date: Wed, 21 Feb 2001 17:27:06 -0500 [thread overview]
Message-ID: <20010221172705.C5113@xi.linuxpower.cx> (raw)
In-Reply-To: <20010220181955.A1994@hobag.internal.zumanetworks.com> <E14VXub-0001vv-00@the-village.bc.nu> <20010221140055.A8113@curtis.curtisfong.org>
In-Reply-To: <20010221140055.A8113@curtis.curtisfong.org>; from nyet@curtis.curtisfong.org on Wed, Feb 21, 2001 at 02:00:55PM -0800
On Wed, Feb 21, 2001 at 02:00:55PM -0800, Nye Liu wrote:
[snip]
> This is NOT what I'm seeing at all.. the kernel load appears to be
> pegged at 100% (or very close to it), the user space app is getting
> enough cpu time to read out about 10-20Mbit, and FURTHERMORE the kernel
> appears to be ACKING ALL the traffic, which I don't understand at all
> (e.g. the transmitter is simply blasting 300MBit of tcp unrestricted)
>
> With udp, we can get the full 300MBit throughput, but only if we shape
> the load to 300Mbit. If we increase the load past 300 MBit, the received
> frames (at the user space udp app) drops to 10-20MBit, again due to
> user-space application scheduling problems.
Perhaps excess context switches are thrashing the system?
prev parent reply other threads:[~2001-02-21 22:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 2:19 Very high bandwith packet based interface and performance problems Nye Liu
[not found] ` <E14VXub-0001vv-00@the-village.bc.nu>
2001-02-21 22:00 ` Nye Liu
2001-02-21 22:07 ` Alan Cox
2001-02-21 22:11 ` Nye Liu
2001-02-21 22:25 ` Alan Cox
2001-02-22 1:24 ` Nye Liu
2001-02-22 1:50 ` Rick Jones
2001-02-22 10:14 ` Alan Cox
2001-02-22 1:46 ` Rick Jones
2001-02-22 10:20 ` Alan Cox
2001-02-22 18:12 ` Rick Jones
2001-02-23 18:27 ` kuznet
2001-02-22 21:48 ` Pavel Machek
2001-02-21 22:27 ` Gregory Maxwell [this message]
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=20010221172705.C5113@xi.linuxpower.cx \
--to=greg@linuxpower.cx \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nyet@curtis.curtisfong.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 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.