All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: "Raúl Hernández" <rauhersu@gmail.com>
Cc: "netdev@vger.kernel.org >> Linux Netdev List" <netdev@vger.kernel.org>
Subject: Re: QoS hot changes changes (tc)
Date: Sat, 27 Jun 2009 23:42:26 +0200	[thread overview]
Message-ID: <4A469242.4070000@gmail.com> (raw)
In-Reply-To: <3f847c820906260619g238b6a17ub17af3f27da83ef5@mail.gmail.com>

Raúl Hernández wrote, On 06/26/2009 03:19 PM:

> Hi there,
> 
> I am trying to characterize the situation in which we perform a change
> in the shaping done by the Linux kernel (tc+qdisc), specifically when
> modifying the bandwidth as a hot change while shaping with a previous
> bw value. The system I am describing performs shaping per stream
> (uplink and/or dowinlink or total), just marking the TOS of the ip
> packet and provisioning the kernel via 'tc' to shape the packets.
> 
> My question is whether someone has tried to modify bw parameters, ie:
> move from 90 to 45 kb/s while the queues are already being populated
> with trafffic .Do not know if the shaper algorithm is able to adjust
> the bw without service disruption/experiment transitory behavior as I
> guess the algorithm must have some kind of feedback which depends of
> the bytes already shaped and the value of the bw itself (ie: leaky
> bucket).
> 
> Any experience with this kind of changes :-) ? Thx !

No experience in measuring the effects of such changes, but looking
into code shows it depends on a shaper algorithm: tbf seems to reset
the queue, htb doesn't.

Jarek P.

  reply	other threads:[~2009-06-27 21:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 13:19 QoS hot changes changes (tc) Raúl Hernández
2009-06-27 21:42 ` Jarek Poplawski [this message]
2009-06-30  6:21   ` Raúl Hernández

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=4A469242.4070000@gmail.com \
    --to=jarkao2@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=rauhersu@gmail.com \
    /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.