public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Dave Carrigan <dave@rudedog.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.16: Bizarre TCP throughput problems
Date: Sun, 09 Dec 2001 11:20:26 +0100	[thread overview]
Message-ID: <3C133AEA.50605@colorfullife.com> (raw)

>
>
>cbgb-2.4.16	pern	NFS/UDP		~12 MB/s, .5s to copy a 5MB file
> cbgb-2.4.14	pern	HTTP/TCP	 12 MB/s, .5s to copy a 5MB file
> cbgb-2.4.16	pern	HTTP/TCP	7.45 KB/s, 300s to copy a 2MB file
>
Could you try:
- if concurrent flood pings between cbgb an dpern improve the throughput 
with 2.4.16 and HTTP?
 # ping -f pern
or
# ping -f cbdb

- Could you check what happens with 2.4.16 if you revert to the tulip 
driver from 2.4.14?

Copy the entire linux/drivers/net/tulip/ directory from 2.4.16 into 2.4.14.

--
    Manfred


             reply	other threads:[~2001-12-09 10:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-09 10:20 Manfred Spraul [this message]
2001-12-09 21:16 ` 2.4.16: Bizarre TCP throughput problems Dave Carrigan
  -- strict thread matches above, loose matches on Subject: below --
2001-12-09  0:08 Dave Carrigan

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=3C133AEA.50605@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=dave@rudedog.org \
    --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