All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Wondershaper updates.
Date: Mon, 31 Mar 2003 23:40:11 +0000	[thread overview]
Message-ID: <marc-lartc-104915409910500@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104913989626740@msgid-missing>

Giles,

 : I think I'll use htbinit, seems the most understandable. Seems a waste
 : that people with lots of experience who are very into this stuff don't
 : compile all the findings into a generic script(s) with parameters that
 : any newbie can configure and benefit from.

The problem is a complex one.  If you have thoughts or suggestions about
how a script can be flexibly adapted to solve the problem, your voice is
welcome.  Wondershaper is an excellent example of a traffic control
solution to a niche problem.  It doesn't however address a more complex
scenario.

Your reasoning is exactly why wondershaper, cbq.init, htb.init, and my own
lousy htb-script [1] exist.  I'm sure there are others.  People have
vastly different needs for subdividing their bandwidth, hence the varied
scripts for dividing bandwidth.

Frankly, I believe that tcng [2] will allow people to write and share
traffic control solutions in a much friendlier way than can be
accomplished directly with tc.  So, once again, I recommend that anybody
starting to use traffic control under linux today start with tcng.  It
provides a more intuitive system for describing traffic control structures
than raw tc commands.  And, not only is it more intuitive, but tcng
removes the repetitive and arcane from the configuration.

If you make a traffic control solution which solves a general problem or a
class of problem, document it and post it somewhere, so the world can
benefit from your experience.

Anyway, good luck with htb.init.  It should be able to meet most of your
needs.

-Martin

 [1]  http://linux-ip.net/htb-script
 [2]  http://tcng.sourceforge.net/

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-03-31 23:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31 19:43 [LARTC] Wondershaper updates lartc
2003-03-31 19:58 ` Martin A. Brown
2003-03-31 22:41 ` lartc
2003-03-31 23:40 ` Martin A. Brown [this message]

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=marc-lartc-104915409910500@msgid-missing \
    --to=mabrown-lartc@securepipe.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.