From: vincent perrier <vincent-perrier@club-internet.fr>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Determing the pfifo backlog
Date: Sun, 23 Jan 2005 08:26:55 +0000 [thread overview]
Message-ID: <1106468815.5703.6.camel@localhost.localdomain> (raw)
In-Reply-To: <3d41a0ab2ae2.41f2ee31@Princeton.EDU>
> My first question is whether a command exists that provides info
> about the backlog.
>
> My second question is whether a system call exists that provides this
> info. I would like to be able to query on the backlog at real time
> and invoking the shell on each such query sounds like a lot of overhead.
If you can compile a modified kernel, you can have real time access
to the red qdisc backlog by using the soft at http://www.rawsoft.org
I also think that real time info on the queues are very important
and should be accessible in an easier way.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2005-01-23 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 5:22 [LARTC] Determing the pfifo backlog Ioannis C Avramopoulos (iavramop@Princeton.EDU)
2005-01-23 8:26 ` vincent perrier [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=1106468815.5703.6.camel@localhost.localdomain \
--to=vincent-perrier@club-internet.fr \
--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.