All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: questiona about CBQ algorithm in Linux
Date: Mon, 09 Sep 2002 21:53:14 +0000	[thread overview]
Message-ID: <marc-lartc-103160858825790@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103133728516866@msgid-missing>

heh you was a bit faster Alexey ;-)

On Mon, 9 Sep 2002 kuznet@ms2.inr.ac.ru wrote:

> Hello!
>
> > Sorry for my stubborn question. I read the S.Floyd paer "Link-sharing and
> > resource mamagement...." On page 5, they said" The estimator estimates the
> > bandwidth used byeach class over the appropriate time interval, to determine
> > whether or not each class has been receiveing its link -sharing
> > bandwidth..."
>
> Appendix A.
>
>
> > sch_cbq.c comments, not quite sure one line" Linux has no EOI event, so that
> > we ca not estimater true idle class idle time..."
> > what's EOI event, This is why in Linux, CBQ canot measure bandwidth?
>
> No. No OSes have "EOI event". :-)
>
> CBQ does not measure bandwidth because it does not need it. Period.
> Listen, please, do not waste your time for useless phylosophical meditations,
> read the paper instead.
>
> Alexey
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>

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

      parent reply	other threads:[~2002-09-09 21:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06 18:31 [LARTC] Re: questiona about CBQ algorithm in Linux kuznet
2002-09-09 18:05 ` yuxiao
2002-09-09 18:28 ` kuznet
2002-09-09 21:52 ` Martin Devera
2002-09-09 21:53 ` Martin Devera [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-103160858825790@msgid-missing \
    --to=devik@cdi.cz \
    --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.