From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Felix Obenhuber <felix@obenhuber.de>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>, linux-can@vger.kernel.org
Subject: Re: Retrieve amount of queued frames in the txqueue of a interface
Date: Thu, 07 Feb 2013 18:43:51 +0100 [thread overview]
Message-ID: <5113E7D7.4070807@hartkopp.net> (raw)
In-Reply-To: <CAJsOQGMbTkJfc8YYiTdhc9r3aT1mD9MfGmWL3u=DwOmPojNLiw@mail.gmail.com>
On 07.02.2013 17:18, Felix Obenhuber wrote:
> Hi Marc,
>
> On Thu, Feb 7, 2013 at 11:42 AM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
>> On 02/06/2013 12:59 PM, Felix Obenhuber wrote:
>>> Hi,
>>>
>>> how can I retrive the number of frames currently queued for
>>> transmission on a SocketCAN interface? Is this possible via netlink?
>>
>> Sorry, I don't know. What's you usecase?
>
> We're working with ISOBUS systems (ISO11783). During a transport
> protocol session (similiar to iso tp) we'd like to know how many
> frames can get queued at once to adjust timings. There are multiple
> software modules that might send frames at the same time over a
> single module/socket.
>
> Maybe we have to add a tx fifo within the software...
Probably the Linux queueing disciplines for CAN are interesting for you:
http://rtime.felk.cvut.cz/can/socketcan-qdisc-final.pdf
The funtionality is part of the Linux Kernel since 3.6.
Regards,
Oliver
next prev parent reply other threads:[~2013-02-07 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 11:59 Retrieve amount of queued frames in the txqueue of a interface Felix Obenhuber
2013-02-07 10:42 ` Marc Kleine-Budde
2013-02-07 16:18 ` Felix Obenhuber
2013-02-07 17:43 ` Oliver Hartkopp [this message]
2013-02-13 8:59 ` isobus with transport protocol Kurt Van Dijck
2013-02-14 8:53 ` Felix Obenhuber
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=5113E7D7.4070807@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=felix@obenhuber.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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).