Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Srikanth <srikanth_w@naturesoft.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ DEVICE BW?
Date: Sat, 24 May 2003 04:30:55 +0000	[thread overview]
Message-ID: <marc-lartc-105375023603422@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105367981700469@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]

Thanks Stef,

I've customized ethtool source, it's giving the correct values depends 
on the real
physical I/F BW. (as per my requirements)

I need only speed from that.

Stef Coene wrote:

>>Forgive me, if i'm wrong.
>>
>>As of my understanding, are the below lines right?
>>
>>DEVICE BW = Real physical bandwidth of the device
>>
>>So, Here DEVICE means only the Interface, not the Link, am i right?
>>    
>>
>Yes.
>
>>&
>>
>>RATE = Rate assigned to perticular user/network/service.
>>
>>How much the user/network/service can aquire max. allowable rate?
>>    
>>
>Yes.  If you add the bounded parameter, you create a maximum for that class.
>
>>I can consider as 10/100 Mbps for ethernet interface.
>>So, how about, when i use ppp0 (pppoe) in my CBQ, is it same?
>>bcoz, pppoe uses eth0, am i right?
>>    
>>
>I'm not sure about that.  But I think you have to use the eth0 speed.
>Or use htb, no more bandwidth questions needed :)
>
Yah, from now onwards, no more DEVICE BW questions.

>Stef
>
>  
>
Srikanth.

[-- Attachment #2: Type: text/html, Size: 1635 bytes --]

      parent reply	other threads:[~2003-05-24  4:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23  8:56 [LARTC] CBQ DEVICE BW? Srikanth
2003-05-23 10:14 ` Stef Coene
2003-05-23 11:49 ` Srikanth
2003-05-23 12:38 ` Srikanth
2003-05-23 16:53 ` Stef Coene
2003-05-24  4:30 ` Srikanth [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-105375023603422@msgid-missing \
    --to=srikanth_w@naturesoft.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox