Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Justin Schoeman <justin@expertron.co.za>
To: netfilter@lists.netfilter.org
Subject: Alternatives to window shaping?
Date: Thu, 30 Aug 2007 12:45:43 +0200	[thread overview]
Message-ID: <46D69FD7.3000405@expertron.co.za> (raw)

I have posted this before under another thread, but did not get many 
replies. So I thought I would post it under a more appropriate subject.

OK, so we have a link that has a fair bandwidth, and a high latency. 
This means that TCP windows get nice and big.

Now I have a problem with ingress shaping, because the current 
implementation just drops packets.  This means that we have to wait for 
the sender to notice the packet drop (OK, or for the receiver to notice 
at out of order inbound backet). But either of these can take quite a 
while, during which the sender is still sending data at a rate higher 
than what you want to throttle it to.

What I was considering was, instead of just dropping the packet, send 
out an ACK packet (to the sender of the packet we are dropping), 
repeating the last ack sequence, as recorded in the conntrack table.

This should be the second ack the sender receives, which should 
immediately start a 'slow start' procedure, and get the sender to back off.

This is still as wastefull as just dropping the packet, but should have 
a more immediate effect.

The problem is, how will the sender and receiver respond? They may now 
receive a number of packets in completely unexpected order.

Is this practical? Will it work? Will it help?

Thanks!
Justin


             reply	other threads:[~2007-08-30 10:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 10:45 Justin Schoeman [this message]
2007-08-30 15:14 ` Alternatives to window shaping? Gregory Carter
2007-08-30 20:56 ` Jorge Davila

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=46D69FD7.3000405@expertron.co.za \
    --to=justin@expertron.co.za \
    --cc=netfilter@lists.netfilter.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