public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: DervishD <raul@pleyades.net>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: QoS on incoming data
Date: Tue, 11 Jun 2002 21:30:47 +0200	[thread overview]
Message-ID: <3D064FE7.mail1Z311DBJT@viadomus.com> (raw)

    Hi all :)

    After reading a bit of the HOWTO about traffic control and
advanced routing, I have a doubt about the queue disciplines and
traffic shaping.

    I've seen that, except the 'ingress' qdisc (and maybe the
hierarchycal token bucket) all other qdisc's seem to be only valid
for outgoing traffic, although I suppose that some of those qdisc
could be easily applied to incoming traffic.

    But the key point is that: I think that the better way of
controlling the incoming bandwidth is the Token Bucket Filter, just
as the autor of the HOWTO says, but I think (may be wrong here) that
the TBF is only valid for outgoing traffic. Moreover, if, just as the
HOWTO says, we set up the TBF for controlling the incoming traffic at,
lets say, 250kb/s for an ADSL access of 256kb/s, it won't control the
outgoing traffic, since the bandwidth of that traffic is just
128kb/s. That is: TBF is not valid if applied to both incoming and
outgoing traffic, and anyway I think that only controls the outgoing
part.

    Please excuse the continous questions about this subject, but I'm
new to this and wanting to understand a bit this powerful feature.

    Thanks in advance :)
    Raúl

             reply	other threads:[~2002-06-11 19:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-11 19:30 DervishD [this message]
2002-06-11 20:07 ` QoS on incoming data Christopher E. Brown
2002-06-11 20:57 ` Anders Eriksson
2002-06-12  8:45   ` DervishD

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=3D064FE7.mail1Z311DBJT@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