All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roy" <roy@xxx.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] When the inside functions of a sfq are called ?
Date: Fri, 16 Apr 2004 00:47:09 +0000	[thread overview]
Message-ID: <000901c4234c$5a405a30$030aa8c0@t> (raw)
In-Reply-To: <3536.192.193.194.7.1082049009.squirrel@mail.smartcall.ro>

Logicaly it would be so:
enqueue caled by last(leaf) filter
dequeue called by htb
drop should not be used in normal operation, probably called on "tc dev eth0
del root"

(this is what I think it should be not nessecary t is so)

----- Original Message ----- 
From: "Adrian Saileanu" <adrian@smartcall.ro>
To: <lartc@mailman.ds9a.nl>
Sent: Thursday, April 15, 2004 8:10 PM
Subject: [LARTC] When the inside functions of a sfq are called ?


>
>   I read the sched/qdiscs code from kernel source ... and I have some
> questions :
>
>   When the .enqueue, .dequeue, .drop, .requeue functions are called ? What
> is the event that triggers them and how often this event apears ( per
> second ? ) ? When a qdisc is dequeued ( when it's limit is reached ) ?
>
>   Thanks
>
>
>
>
>
> _______________________________________________
> 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/

  reply	other threads:[~2004-04-16  0:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15 17:10 [LARTC] When the inside functions of a sfq are called ? Adrian Saileanu
2004-04-16  0:47 ` Roy [this message]
2004-04-16 12:24 ` Adrian Saileanu
2004-04-16 13:00 ` Roy
2004-04-18 10:05 ` Andy Furniss
2004-04-19 13:40 ` Adrian Saileanu
2004-04-19 14:55 ` Andy Furniss

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='000901c4234c$5a405a30$030aa8c0@t' \
    --to=roy@xxx.lt \
    --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.