From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] P2P shaping working
Date: Sat, 09 Jul 2005 16:17:08 +0000 [thread overview]
Message-ID: <42CFF884.B71A2D24@iswest.com> (raw)
In-Reply-To: <200507081926.56750.donvodka@gmail.com>
Edgar wrote:
>
> Hello, it's me again, finally p2p traffic is getting shaped, but now I still
> have one problem: download seems to be affected when shaping the traffic, ack
> packets are in the interactive queue too, as someone adviced me, what fixed
> the problem was to change the rates, to match (the sum of all subclasses) the
> root class rate, and to give the p2p class a very low rate (1k actually) and
> 75% of the bandwidth for the ceiling. Well as I said this is working, but
> downloading seems to be affected to, I get pretty low rates (this doesn't
> happen when I'm not shaping the traffic, but then I can't do anything else
> but bittorrent). Does anyone have a clue on why's this happening?
>
> Thanks to everyone that help me, I really appreciate it.
>
> EDGAR MERINO
Guess 1: You are not giving the ACK to the downloaded packet priority so it
gets delayed.
Guess 2: You are dropping incoming packets, causing resends.
Guess 3: The outbound queue(s) are full so the ACK can't be sent "NOW,
DAMNIT"!
Guess 4: You have not tweaked /etc/sysctl.conf and run sysctl, so the
internal buffers are too small.
Guess 5: Your CPU is overloaded by the queuing.
Guess 6: Your IMQ is misconfigured.
AFAIC, ACK and window size are the most important issues. You must prioritize
the ACKs not associated with file sharing and delay the hell out of those that
are associated with file sharing.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-07-09 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 0:26 [LARTC] P2P shaping working Edgar
2005-07-09 16:17 ` gypsy [this message]
2005-07-10 19:23 ` 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=42CFF884.B71A2D24@iswest.com \
--to=gypsy@iswest.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.