All of lore.kernel.org
 help / color / mirror / Atom feed
From: thunder7@xs4all.nl
To: linux-kernel@vger.kernel.org
Subject: Re: [lkml]2.2.19pre13: Are there network problem with a low-bandwidth link?
Date: Tue, 20 Feb 2001 12:34:57 +0100	[thread overview]
Message-ID: <20010220123457.A679@middle.of.nowhere> (raw)
In-Reply-To: <Pine.LNX.4.21.0102190828120.190-100000@perfect.master>
In-Reply-To: <Pine.LNX.4.21.0102190828120.190-100000@perfect.master>; from tenthumbs@cybernex.net on Mon, Feb 19, 2001 at 08:38:43AM -0500

On Mon, Feb 19, 2001 at 08:38:43AM -0500, TenThumbs wrote:
> When I am a) using modem ppp connection and b) downloading a file from a
> reasonably fast server so that the incoming connection is saturated,
> then attempting to open a new network tcp connection while this is going
> on fails quite regularly. The user app gets a ECONNRESET error.
> 
<snip>
> This never happens if the link is idle or lightly loaded. Heavy load is
> extremely important.
> 
I also saw this when my 2.2.19pre12/13 workstation connected to a
2.2.19pre8 isdn-router. When downloading a large file via ftp at max
speed, other connections don't 'get through'.

Perhaps other people can agree/disagree on this?

Jurriaan
-- 
I never deny, I never contradict. I sometimes forget.
        Benjamin Disraeli
GNU/Linux 2.4.1-ac19 SMP/ReiserFS 2x1402 bogomips load av: 0.01 0.06 0.26

  reply	other threads:[~2001-02-20 11:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-19 13:38 2.2.19pre13: Are there network problem with a low-bandwidth link? TenThumbs
2001-02-20 11:34 ` thunder7 [this message]
2001-02-20 12:39   ` [lkml]2.2.19pre13: " Alan Cox
2001-02-21 14:06     ` TenThumbs
2001-02-21 14:27       ` [lkml]2.2.19pre13: Are there network problem with a low-bandwidth Alan Cox
2001-02-21 13:11   ` [lkml]2.2.19pre13: Are there network problem with a low-bandwidth link? Michèl Alexandre Salim

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=20010220123457.A679@middle.of.nowhere \
    --to=thunder7@xs4all.nl \
    --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 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.