From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: More on qdiscs - about dangling backlogs
Date: Thu, 09 May 2002 11:53:17 +0000 [thread overview]
Message-ID: <marc-lartc-102094527624499@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102058802801083@msgid-missing>
> > right. What you know:
> > - each qdisc's (own) qlen is valid at all (for us important) times
> > - qdisc's qlen can increase only after successfull (!) enqueue
> But I think there's another case - requeue. Maybe you consider that
> the same as enqueue.
> (I've never seen evidence that it was executed, but it's called in
> sch_generic.c)
It should be handled in the same way as requeue only should not increase
stats.
> I still think it's reasonable to check only at dequeue. Basically if
> you know max time between dequeues is t, then a queue filled by a
> flood can only remain full for time t + expire_time after the flood
> ends. After that there will be a dequeue that throws out all the
> flood packets. Then your next packet will be accepted and delayed at
> most expire_time.
It might be. Why don't you try it ? I feel still the same about it: I
think that experiment is the only way to test the idea.
devik
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-05-09 11:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-05 8:39 [LARTC] Re: More on qdiscs - about dangling backlogs Martin Devera
2002-05-06 0:23 ` Don Cohen
2002-05-06 21:31 ` Martin Devera
2002-05-06 23:48 ` Don Cohen
2002-05-07 2:11 ` Patrick McHardy
2002-05-07 5:11 ` Don Cohen
2002-05-07 7:29 ` Martin Devera
2002-05-07 7:50 ` Martin Devera
2002-05-07 7:57 ` Martin Devera
2002-05-07 18:22 ` Don Cohen
2002-05-07 18:45 ` Patrick McHardy
2002-05-07 19:20 ` Don Cohen
2002-05-09 11:53 ` Martin Devera [this message]
2002-05-09 13:46 ` Don Cohen
2002-05-09 14:43 ` Martin Devera
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-102094527624499@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.