From: Benedikt Spranger <b.spranger@linutronix.de>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
Wolfgang Grandegger <wg@grandegger.com>,
linux-can <linux-can@vger.kernel.org>
Subject: Re: API to support hardware priorities
Date: Mon, 9 Nov 2015 16:27:03 +0100 [thread overview]
Message-ID: <20151109162703.3fd6d4fc@mitra> (raw)
In-Reply-To: <5640A4E4.6020005@pengutronix.de>
On Mon, 9 Nov 2015 14:51:32 +0100
Marc Kleine-Budde <mkl@pengutronix.de> wrote:
> Are we talking about RX or TX here?
TX.
> Do you mean the mailbox feature, where you queue a frame into
> hardware, but sending is delayed until a certain CAN-ID is RX'ed?
No.
The C-CAN/D-CAN and some other Controller can be configured to have
mailboxes for a certain Id. For example you can configure MBX 1 for
Id 23, MBX 2 for Id 42 and 3-7 act as FIFO. So every packet matching Id
23 should queued up to MBX 1, every package matching Id 42 to MBX 2 and
all other Packages to the FIFO.
Having a multiqueue TX part may help but may have some drawbacks. If the
FIFO (or an other queue) is full the driver calls netif_stop_queue().
Sending bulk data can block out a "high priority" Package. On the other
hand a application writing bulk data in blocking mode should not
receive a EAGAIN and not be punished by a "mixed up" queue i.e.
violating the package send order.
Regards
Bene
--
Linutronix GmbH
Phone: +49 7556 4521 890; Fax.: +49 7556 91 98 86
Firmensitz: D-88690 Uhldingen, Auf dem Berg 3
Registergericht: Freiburg i. Br., HRB 700 806;
Geschäftsführer: Heinz Egger, Thomas Gleixner
next prev parent reply other threads:[~2015-11-09 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151109123618.41ad1bae@mitra>
2015-11-09 13:32 ` API to support hardware priorities (was: Re: API zur hardwareunterstützten Priorisierung von CAN-Paketen) Marc Kleine-Budde
2015-11-09 13:51 ` API to support hardware priorities Marc Kleine-Budde
2015-11-09 14:04 ` Oliver Hartkopp
2015-11-09 15:27 ` Benedikt Spranger [this message]
2015-11-09 15:38 ` Marc Kleine-Budde
2015-11-09 16:36 ` Benedikt Spranger
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=20151109162703.3fd6d4fc@mitra \
--to=b.spranger@linutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--cc=wg@grandegger.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 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).