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] Coding for Linux Traffic Controller
Date: Sun, 30 Nov 2003 20:26:47 +0000	[thread overview]
Message-ID: <marc-lartc-107022449101932@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107021321825532@msgid-missing>

Hello Kalaiselvan,

 :   I am trying to do Linux Traffic Controller. I am struggling how to
 : start & how to proceed. Help me in sample codings or some useful linux
 : web sites.

I'd suggest some introductory reading....first my own traffic control
overview (and some links to other documentation):

  http://tldp.org/HOWTO/Traffic-Control-HOWTO/
  http://tldp.org/HOWTO/Traffic-Control-HOWTO/links.html

An alternative introduction is Leonardo Balliache's pages:

  http://opalsoft.net/qos/DS.htm

Werner Almesberger's still relevant implementation overview of 1999
warrants (and rewards) careful study:

  http://www.almesberger.net/cv/papers.html
  http://www.almesberger.net/cv/papers/tcio8.pdf

Once you have an understanding of the entire traffic control system, the
easiest way to some practical configurations is with the tcng software:

  http://tcng.sourceforge.net/

I have a few annotated examples of tcng configurations available:

  http://tldp.org/HOWTO/Traffic-Control-tcng-HTB-HOWTO/

There are quite a few lurkers here who use tcng and will help you out as
you get your feet wet.

-Martin

-- 
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-11-30 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-30 17:30 [LARTC] Coding for Linux Traffic Controller Kalai Selvan
2003-11-30 17:53 ` Artūras Šlajus
2003-11-30 20:26 ` Martin A. Brown [this message]
2003-11-30 22:39 ` Martin A. Brown

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-107022449101932@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.