All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Unshapeable traffic
Date: Wed, 04 May 2005 14:18:50 +0000	[thread overview]
Message-ID: <4278D9CA.9070809@dsl.pipex.com> (raw)
In-Reply-To: <1294422007.20050503233431@wp.pl>

Tomasz Wrona wrote:
> AK>  Every new connection will try to push out as
> AK> much data as possible, so HTB is busy beating the little bugger down
> AK> right from the beginning. Some people use iptables to generally drop
> AK> a few packets of any newly established connection to avoid this sort
> AK> of problem.
> 
> To avoid congestion I attached RED queue to p2p class but without any visible effect.
> I doesn't respond on any kind of shaping :/
> 
> 

Maybe you could try further seperating the P2P traffic into bulk and 
network udp/syns/acks etc. Depends on what type of P2P clients are,to 
some extent what tcp there OS is running and number of connections. 
Maybe PRIO would be better with bulk going to SFQ and small packets 
getting priority. You could also play around with queue lengths and see 
if that helps.

Does it actually matter anyway - as it's egress you are shaping and I 
assume the 2Mbit extra doesn't really hurt LAN speeds.

Andy.

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-05-04 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03 21:34 [LARTC] Unshapeable traffic Tomasz Wrona
2005-05-03 22:51 ` Andreas Klauer
2005-05-04  9:00 ` tw
2005-05-04  9:47 ` Andreas Klauer
2005-05-04 14:18 ` Andy Furniss [this message]
2005-05-04 14:58 ` Andy Furniss
2005-05-04 18:54 ` Andy Furniss

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=4278D9CA.9070809@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --cc=lartc@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.