Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Claudio Greco <cla.greco@fastwebnet.it>
To: lartc@vger.kernel.org
Subject: [LARTC] Watchdog timer and packet enqueuing
Date: Thu, 31 May 2007 10:29:15 +0000	[thread overview]
Message-ID: <465EA37B.4030709@fastwebnet.it> (raw)

Hello everybody,

I'm implementing a qdisc for my MSc thesis and I've experienced some 
issue maybe you can help me with.

The discipline is simply a slotted max-weight in which any user has a 
Ceil Rate they mustn't trespass on.

Being such a discipline non-work-conserving,  I've to set a watchdog 
timer in order to allow further call of the dequeue function.

However, I've noticed that such a solution prevents the local generated 
packets to be enqueued, which is very concerning to me being the 
priority based on the backlog...

Does anyone know any trade-off solution between these needs 
(non-conserving-work and continuous enqueue flow)?

Thanks in advance,
Claudio.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

                 reply	other threads:[~2007-05-31 10:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=465EA37B.4030709@fastwebnet.it \
    --to=cla.greco@fastwebnet.it \
    --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