From: Jarek Poplawski <jarkao2@o2.pl>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: hadi@cyberus.ca, netdev@vger.kernel.org
Subject: Re: HTB/HSFC shaping precision
Date: Wed, 21 Nov 2007 10:47:10 +0100 [thread overview]
Message-ID: <20071121094710.GA2295@ff.dom.local> (raw)
In-Reply-To: <20071120211258.M55249@visp.net.lb>
On 20-11-2007 22:21, Denys Fedoryshchenko wrote:
...
> If traffic is dropped - it will be resent, a lot of energy will be wasted for
> nothing. Same bytes will pass all long way around earth just because i am not
> able to manage my QoS box :-)
Sure, but you'll use probably almost every bit you've payed for!
>
> Plus uplink bandwidth will be used for that, i am using my own protocol(it is
> TCP "accelerator" for satellite communications based on NACK and "streaming"
> compression, so each resend - it is few bytes more on uplink and additional
> delay. Ah yes, even resend over TCP it is more delay, than if it will be
> queued for few milliseconds on bottleneck.
>
> Plus if buffer on STM-1 interface way too small - smallest spike will cause
> packetlossy, and sitation can be far away from congestion. As result it will
> be very difficult to reach maximum bandwidth on such link. And linux box in
> this situation is magic box, which can help to save energy, hungry people and
> help to use resources efficiently :-)
>
I'm still not sure how this traffic goes around, because eg., if you
receive something through a satelite, then it would only make sense if
it were controlled earlier to the same speed too. Otherwise you should
have this dropping on your HTB (of course you could use big buffers,
but anyway...), instead of STM, but resending could be similar.
But, if you have full control on your side, it looks like a kind of
realtime traffic, and then HFSC should be more appropriate for this
(but I only 'heard' about this).
> Yes, for sure. Thats what i am reading almost each day, when i dont
> understand something clearly. But, my english is far away from good, so
> sometimes i just misunderstand something even in good manual.
Then good news: read the code! There is really as little English as
possible...
Cheers,
Jarek P.
next prev parent reply other threads:[~2007-11-21 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 8:55 HTB/HSFC shaping precision Denys Fedoryshchenko
2007-11-19 16:24 ` jamal
2007-11-20 9:43 ` Denys Fedoryshchenko
2007-11-20 20:00 ` Jarek Poplawski
2007-11-20 21:21 ` Denys Fedoryshchenko
2007-11-21 9:47 ` Jarek Poplawski [this message]
2007-11-21 10:31 ` Denys Fedoryshchenko
2007-11-21 15:06 ` jamal
2007-11-22 2:07 ` Ryousei Takano
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=20071121094710.GA2295@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=denys@visp.net.lb \
--cc=hadi@cyberus.ca \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).