From: DervishD <raul@pleyades.net>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Bandwidth 'depredation' revisited
Date: Tue, 11 Jun 2002 14:35:59 +0200 [thread overview]
Message-ID: <3D05EEAF.mailZE11URHZ@viadomus.com> (raw)
Hi all :))
I've took a look at the documentation related to Traffic Control
and Class Based Queuing, but all of them seems to deal with upload
bandwidth, so it won't solve my problem, which is that wget eats all
my download bandwidth.
I know: downlink traffic cannot be shaped and Traffic Control is
for data WE send. So, am I missing something? Will my problem be solved
and download bandwidth shared between apps thru Traffic Control or
will I just get better interactive response?
I think that I'm missing something here, but I'm clueless...
Thanks in advance :)
Raúl
next reply other threads:[~2002-06-11 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 12:35 DervishD [this message]
2002-06-11 14:57 ` Bandwidth 'depredation' revisited Anders Fugmann
2002-06-11 17:18 ` DervishD
2002-06-11 18:25 ` Anders Peter Fugmann
2002-06-11 20:20 ` Marius Gedminas
2002-06-11 20:59 ` Allan Sandfeld Jensen
2002-06-14 3:35 ` Albert D. Cahalan
2002-06-14 9:16 ` Anders Peter Fugmann
2002-06-14 9:17 ` lkml
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=3D05EEAF.mailZE11URHZ@viadomus.com \
--to=raul@pleyades.net \
--cc=linux-kernel@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