From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Efim Monjak <emonjak@lipowsky.de>,
linux-can@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: at91 driver lost CAN messages
Date: Mon, 13 Mar 2017 07:54:30 +0100 [thread overview]
Message-ID: <3972105.9n1vzaBFN5@ws-stein> (raw)
In-Reply-To: <ee9c0d9d-6cd6-f93b-2f2b-8306777781c3@hartkopp.net>
On Sunday 12 March 2017 00:06:02, Oliver Hartkopp wrote:
> Hi Efim,
>
> On 03/10/2017 02:48 PM, Efim Monjak wrote:
> > If napi polling is deactivated by follow change no more receive overflow
> > error occurs.
>
> thanks for the patch!
>
> In fact I always thought NAPI is too heavy for CAN controllers. NAPI was
> intended for a very high interrupt load on some ethernet controllers
> with some considerable RX FIFO.
>
> I have a 20 CAN interfaces (SJA1000 driver) Core i7 system receiving
> ~22.000 frames/s without any problems, with an one-element FIFO and
> without NAPI.
>
> @Marc: What was the reason to implement NAPI that days? Has it ever been
> proved that NAPI had a remarkable positive effect in opposite to a
> direct CAN frame processing in the interrupt context?
One reason to use NAPI is out-of-order issues on SMP systems :-( You know the
problem: http://marc.info/?l=linux-can&m=143642135416355&w=2
If this is not resolved, things get even worse.
Well, now that there is generic FIFO-offload feature (drivers may need changes
to use it) there is an easy way to read CAN frames with low latency while
processing them in non-IRQ context.
IMHO reading CAN frames in softirq (NAPI) may be too late in some cases, in RT
kernels this may be even worse.
Best regards,
Alexander
--
Dipl.-Inf. Alexander Stein
SYS TEC electronic GmbH
alexander.stein@systec-electronic.com
Legal and Commercial Address:
Am Windrad 2
08468 Heinsdorfergrund
Germany
Office: +49 (0) 3765 38600-0
Fax: +49 (0) 3765 38600-4100
Managing Directors:
Director Technology/CEO: Dipl.-Phys. Siegmar Schmidt;
Director Commercial Affairs/COO: Dipl. Ing. (FH) Armin von Collrepp
Commercial Registry:
Amtsgericht Chemnitz, HRB 28082; USt.-Id Nr. DE150534010
next prev parent reply other threads:[~2017-03-13 6:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 13:48 at91 driver lost CAN messages Efim Monjak
2017-03-11 23:06 ` Oliver Hartkopp
2017-03-13 6:54 ` Alexander Stein [this message]
2017-03-13 9:47 ` Marc Kleine-Budde
2017-03-16 8:01 ` Oliver Hartkopp
2017-03-16 8:34 ` Marc Kleine-Budde
2017-03-16 9:06 ` Alexander Stein
2017-03-16 9:09 ` Oliver Hartkopp
2017-03-16 9:58 ` Alexander Stein
2017-03-16 10:18 ` Marc Kleine-Budde
2017-03-20 7:38 ` Alexander Stein
2017-03-16 9:07 ` Oliver Hartkopp
2017-03-16 9:24 ` Efim Monjak
2017-03-16 9:32 ` Marc Kleine-Budde
2017-03-16 10:06 ` Efim Monjak
2017-03-16 10:11 ` Marc Kleine-Budde
2017-03-13 9:47 ` Marc Kleine-Budde
2017-03-13 12:55 ` Efim Monjak
2017-03-13 13:11 ` Marc Kleine-Budde
2017-03-13 15:17 ` Efim Monjak
2017-03-13 14:23 ` Marc Kleine-Budde
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=3972105.9n1vzaBFN5@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=emonjak@lipowsky.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
/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