From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Inspection of SFQ work
Date: Thu, 20 Dec 2001 22:02:52 +0000 [thread overview]
Message-ID: <marc-lartc-100888581406593@msgid-missing> (raw)
Is there any way / patch allowing inspection of decisions made by various
qdiscs? I'm particularly interested in SFQ and RED but I'm sure following
the logic flow in CBQ would be enlightening as well ;-).
To the point, something that logs all the decisions made;
[timestamp] queued packet [header] [hashval]
[timestamp] dequeued packet [header] [hashval]
[timestamp] dequeued packet [header] [hashval]
... I'm sure it would slow things down, but there are some occasions where
turning this kind of thing on is 'smart'.
Just wondering
--
Michael T. Babcock
CTO, FibreSpeed Ltd. (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next reply other threads:[~2001-12-20 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 22:02 Michael T. Babcock [this message]
2001-12-20 22:14 ` [LARTC] Inspection of SFQ work bert hubert
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-100888581406593@msgid-missing \
--to=mbabcock@fibrespeed.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