All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sipat Triukose <sxt85@case.edu>
To: lartc@vger.kernel.org
Subject: [LARTC] Data collection in Linux TC queue
Date: Tue, 13 Jul 2004 10:01:19 +0000	[thread overview]
Message-ID: <1089712879.3443.7.camel@localhost.localdomain> (raw)

Dear All,

Would you guy have any advices concerning how to get some data like
queue length, pkt size, and so forth, from the running queue. 

Right now, I modified the queue disc to print out some info I want using
printk() and use syslogd to catch those info up. The problem is, in
burst, syslogd can't catch all the msg the queue sent out. 

Are there any standard or better way to collect those info from the
queue disc ? 

Thank you very much in advance for every advices.

-- 
Sipat Triukose <sxt85@case.edu>
Case Western Reserve University

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2004-07-13 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 10:01 Sipat Triukose [this message]
2004-07-13 10:13 ` [LARTC] Data collection in Linux TC queue Catalin BOIE
2004-07-13 10:41 ` Sipat Triukose
2004-07-13 10:49 ` Catalin BOIE

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=1089712879.3443.7.camel@localhost.localdomain \
    --to=sxt85@case.edu \
    --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.