From: Andi Kleen <andi@firstfloor.org>
To: clownix <clownix@clownix.net>
Cc: netdev@vger.kernel.org
Subject: Re: New qdisc monitor
Date: Fri, 02 Oct 2009 23:21:22 +0200 [thread overview]
Message-ID: <873a61bigd.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1254501684.2670.7.camel@localhost> (clownix@clownix.net's message of "Fri, 02 Oct 2009 18:41:24 +0200")
clownix <clownix@clownix.net> writes:
> At http://clownix.net, there is a qdisc monitor based on a new sched
> qdisc named spy and a module that periodicaly sends the
> enqueues/dequeues/drops/queue-size/delays... to be plotted to the user
> world through a netlink socket.
> Note that the name of this software package is "clownix_spy", and not
> cloonix_net which is another project on the same site.
Sounds like a cool idea, but could you consider submitting the qdisc
for mainline and getting it reviewed? Out of tree kernel patches for these
kinds of things tend to be a pain to use.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2009-10-02 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 16:41 New qdisc monitor clownix
2009-10-02 21:21 ` Andi Kleen [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=873a61bigd.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=clownix@clownix.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).