From: Tom Evans <tom_usenet@optusnet.com.au>
To: Paarvai Naai <opensource3141@gmail.com>,
Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Dan Egnor <dan.egnor@gmail.com>, linux-can@vger.kernel.org
Subject: Re: Fwd: Querying current tx_queue usage of a SocketCAN interface
Date: Fri, 03 Apr 2015 12:35:56 +1100 [thread overview]
Message-ID: <551DEE7C.6040202@optusnet.com.au> (raw)
In-Reply-To: <CAE+ymrv2mf1Cn+9EQgyS5yhSxFdSadRKvwb_opLm8AkKqfqV5w@mail.gmail.com>
On 3/04/2015 5:28 AM, Paarvai Naai wrote:
> Ironically, that brings us full-circle back to my original reason for
> this thread, but we went off on a tangent in the meantime (partly my
> fault!). Querying the tx_queue usage has multiple benefits. Is there
> some way we can address that easier issue first?
Didn't I already answer that question a few days ago?
I found something in /proc or /sys (details in my mailbox at work) That
looked like the interface to qdisc to allow inspection of the queue depths.
Thanks to google that's:
cat /sys/class/net/can0/queues/tx-0/byte_queue_limits/inflight
drivers/net/core/net-sysfs.c
/lib/dynamic_queue_limits.c
Did you investigate that at all, or are you waiting for someone else to
do this for you?
Can anyone else comment on that apparent interface? Is "dql" part of
"qdisc" or something else? How is it enabled?
---
Before using google I just spent 30 minutes trying to quote my previous
reply from:
http://dir.gmane.org/gmane.linux.can
Can anyone else get to the above URL today? It crashes Firefox every
time I go there, locks up IE solidly, and I gave up on lynx after it
started running GZIP and pulling down about 10 MEGS of data without
displaying anything.
It is now spitting "fopen()", "feof()" and "fgets()" PHP errors at me,
so it looks like gmane is broken for Easter.
Tom
next prev parent reply other threads:[~2015-04-03 1:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAE+ymru296P+LjkT7_ONVc2OGMP9mtXW46Nq5aSnm1etauj9Aw@mail.gmail.com>
2015-03-28 20:26 ` Fwd: Querying current tx_queue usage of a SocketCAN interface Paarvai Naai
2015-03-29 22:42 ` Tom Evans
2015-03-30 21:55 ` Paarvai Naai
[not found] ` <5519E5A9.7080104@optusnet.com.au>
2015-03-31 0:26 ` Paarvai Naai
2015-03-31 3:09 ` Tom Evans
2015-04-01 20:33 ` Paarvai Naai
2015-04-01 20:57 ` Dan Egnor
2015-04-02 2:20 ` Tom Evans
2015-04-02 2:33 ` Daniel Egnor
2015-04-01 23:21 ` Tom Evans
2015-04-02 0:33 ` Dan Egnor
2015-04-02 2:20 ` Tom Evans
2015-04-02 6:28 ` Flexcan (was: Re: Fwd: Querying current tx_queue usage of a SocketCAN interface) Marc Kleine-Budde
2015-04-02 11:35 ` Tom Evans
2015-04-02 12:07 ` Flexcan Marc Kleine-Budde
2015-04-04 3:32 ` Flexcan (was: Re: Fwd: Querying current tx_queue usage of a SocketCAN interface) Tom Evans
2015-04-09 8:06 ` Flexcan Tom Evans
2015-04-10 6:35 ` Flexcan (was: Re: Fwd: Querying current tx_queue usage of a SocketCAN interface) Tom Evans
2015-04-02 18:23 ` Fwd: Querying current tx_queue usage of a SocketCAN interface Paarvai Naai
2015-04-02 6:46 ` Marc Kleine-Budde
2015-04-02 18:28 ` Paarvai Naai
2015-04-03 1:35 ` Tom Evans [this message]
2015-04-03 6:45 ` Paarvai Naai
2015-04-03 11:08 ` Marc Kleine-Budde
2015-04-03 15:24 ` Paarvai Naai
2015-04-03 20:28 ` Marc Kleine-Budde
2015-04-03 20:53 ` Paarvai Naai
2015-04-04 8:49 ` Marc Kleine-Budde
2015-04-06 17:54 ` Paarvai Naai
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=551DEE7C.6040202@optusnet.com.au \
--to=tom_usenet@optusnet.com.au \
--cc=dan.egnor@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=opensource3141@gmail.com \
/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.