All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: "David S. Miller" <davem@redhat.com>
Cc: bert hubert <ahu@ds9a.nl>, Ben Greear <greearb@candelatech.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: problems achieving decent throughput with latency.
Date: Mon, 03 Feb 2003 10:37:16 -0500	[thread overview]
Message-ID: <3E3E8CAC.7010807@nortelnetworks.com> (raw)
In-Reply-To: 1044249293.19078.1.camel@rth.ninka.net

David S. Miller wrote:
> TCP can only send into a pipe as fast as it can see the
> ACKs coming back.  That is how TCP clocks its sending rate,
> and latency thus affects that.

Wouldn't you just need larger windows?  The problem is latency, not 
bandwidth.

Chris



-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com


  reply	other threads:[~2003-02-03 15:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02  7:38 problems achieving decent throughput with latency Ben Greear
2003-02-02 11:48 ` bert hubert
2003-02-03  5:14   ` David S. Miller
2003-02-03 15:37     ` Chris Friesen [this message]
2003-02-03 16:11       ` John Bradford
2003-02-03 16:19         ` bert hubert
2003-02-03 18:03         ` Ben Greear
2003-02-03 19:18           ` Eric Weigle
2003-02-04  5:19           ` David S. Miller
2003-02-04  7:50             ` Ben Greear
2003-02-04  7:39               ` David S. Miller
2003-02-04  8:42                 ` Ben Greear
2003-02-04  8:41                   ` David S. Miller
2003-02-04  8:51                   ` Ben Greear
  -- strict thread matches above, loose matches on Subject: below --
2003-02-01 22:13 Ben Greear

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=3E3E8CAC.7010807@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=ahu@ds9a.nl \
    --cc=davem@redhat.com \
    --cc=greearb@candelatech.com \
    --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.