From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Inspection of SFQ work
Date: Thu, 20 Dec 2001 22:14:56 +0000 [thread overview]
Message-ID: <marc-lartc-100888653608384@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100888581406593@msgid-missing>
On Thu, Dec 20, 2001 at 05:02:52PM -0500, Michael T. Babcock wrote:
> 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 ;-).
I've thought about it. There is no easy single entrypoint to do this. Each
qdisc would have its own debugging statements. The good news is that this is
easy to add, just insert 'printk' statements in relevant places.
Kernel policy however is that no 'explanatory' statements are allowed in the
mainline kernel, just as there is no kernel debugger in the mainline kernel.
> ... I'm sure it would slow things down, but there are some occasions where
> turning this kind of thing on is 'smart'.
I'm not sure, but perhaps IBM 'dprobes' might be suited for this work.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2001-12-20 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 22:02 [LARTC] Inspection of SFQ work Michael T. Babcock
2001-12-20 22:14 ` bert hubert [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-100888653608384@msgid-missing \
--to=ahu@ds9a.nl \
--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.