From: Rick Jones <raj@cup.hp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Nye Liu <nyet@curtis.curtisfong.org>, linux-kernel@vger.kernel.org
Subject: Re: Very high bandwith packet based interface and performance problems
Date: Wed, 21 Feb 2001 17:46:25 -0800 [thread overview]
Message-ID: <3A946F71.69D94D13@cup.hp.com> (raw)
In-Reply-To: <E14VhQ7-0002s0-00@the-village.bc.nu>
Alan Cox wrote:
>
> > that because the kernel was getting 99% of the cpu, the application was
> > getting very little, and thus the read wasn't happening fast enough, and
>
> Seems reasonable
>
> > 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)
>
> TCP _requires_ the remote end ack every 2nd frame regardless of progress.
um, I thought the spec says that ACK every 2nd segment is a SHOULD not a
MUST?
rick jones
--
ftp://ftp.cup.hp.com/dist/networking/misc/rachel/
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to email, OR post, but please do NOT do BOTH...
my email address is raj in the cup.hp.com domain...
next prev parent reply other threads:[~2001-02-22 1:46 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 [this message]
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
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=3A946F71.69D94D13@cup.hp.com \
--to=raj@cup.hp.com \
--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.