Netdev List
 help / color / mirror / Atom feed
From: "Taekeun Lee" <tedlee@ece.skku.ac.kr>
To: <netdev@oss.sgi.com>
Subject: Question.. Traffic Shaping in Linux
Date: Mon, 18 Nov 2002 17:52:27 +0900	[thread overview]
Message-ID: <000001c28edf$d2634ed0$0105a8c0@tedlee> (raw)

Hello, My name is Taekeun Lee..

I'm a graduate student in Sungkyunkwan Univ. in Korea..

This e-mail address(netdev@oss.sgi.com) is introduced by Alan Cox..

My Question is Traffic shaping in linux..

Existed traffic shaper in Linux kernel module is possible low bandwidth
limitation.. ( < 1Mbps )

And, High bandwidth limitation can use CBQ kernel facilities..

But, My router is working with RSVP Daemon, RSVP Daemon controls packets
by CBQ mechanism..

So, I can't use CBQ facility for traffic shaping..

 

I want to traffic shaping in Linux without CBQ mechanism..

 

Can U suggest a solution to this problem?

 

I'm sorry, my poor english..



[[HTML alternate version deleted]]

             reply	other threads:[~2002-11-18  8:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18  8:52 Taekeun Lee [this message]
2002-11-19  2:43 ` Question.. Traffic Shaping in Linux jamal

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='000001c28edf$d2634ed0$0105a8c0@tedlee' \
    --to=tedlee@ece.skku.ac.kr \
    --cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox