All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Brenton <cbrenton@chrisbrenton.org>
To: Marcin Sura <slacklist@op.pl>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: [OT] Little TCP/IP question
Date: Sun, 22 Aug 2004 18:58:27 -0400	[thread overview]
Message-ID: <1093215507.1659.5.camel@grendel> (raw)
In-Reply-To: <112010952.20040823004437@op.pl>

On Sun, 2004-08-22 at 18:44, Marcin Sura wrote:
>
>   What is the TCP/IP algorithm that control usage of bandwidth by sessions
>   (flows?)?

This is going to vary based on the window size. Its not surprising that
the first session is getting more bandwidth as its had more time to
negotiate a larger window size and a smaller inter-packet gap. Its also
not surprising that this changes over time due to the latency caused by
the line being saturated.

If you want to even this out, your best bet would be to implement some
QoS. Not sure its so far off that its really worth it though.

HTH,
Chris





      reply	other threads:[~2004-08-22 22:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22 22:44 [OT] Little TCP/IP question Marcin Sura
2004-08-22 22:58 ` Chris Brenton [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=1093215507.1659.5.camel@grendel \
    --to=cbrenton@chrisbrenton.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=slacklist@op.pl \
    /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.