From: Alexander Stein <alexander.stein@systec-electronic.com>
To: David Jander <david@protonic.nl>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org,
Wolfgang Grandegger <wg@grandegger.com>,
Oliver Hartkopp <socketcan@hartkopp.net>,
"Hans J. Koch" <hjk@hansjkoch.de>
Subject: Re: [RESEND] [PATCH] net: CAN: at91_can.c: decrease likelyhood of RX overruns
Date: Mon, 06 Oct 2014 16:14:05 +0200 [thread overview]
Message-ID: <3545685.3jS4Whu5tJ@ws-stein> (raw)
In-Reply-To: <20141006133942.0f1c820b@archvile>
On Monday 06 October 2014 13:39:42, David Jander wrote:
> > > One interesting control-metric would be to monitor the amount of
> > > messages/second your test-devices are able to generate.
> >
> > I just noticed that this testing hardware has a DDR2 with only 16bit
> > interface. I think this will also reduce performance considerably. The
>
> 16-bit DDR2 (even at its lowest clock of 200MHz) is not exactly slow... why do
> you think that could be a bottleneck?
It's a 133MHz clock, so 266MHz effective.
I had done similar tests with i.MX28-EVK which also has only a 16-bit DDR interface. The rusults were horrible. Even without that ethernet bug...
Now, doing the same tests (also CPU and Memory) again, it is worse than a AT91SAM9G20 with 32-bit SDR RAM, which also has 400 MHz. I expected both would be equally.
If you're correct and the RAM is not the bottleneck it seems that the cache (16kByte each, 32kByte on AT91SAM9G20) would be it.
> > embedded device send ~1000 CAN frames/s, each which is an average busload of
> > 20%, but in burst time, it should be 100%.
>
> You mean the bursts of 250 messages you talked about earlier should produce a
> bus load of 100%? I think it is important to get some certainty about what's
> really going on on the bus, specially if we see things we cannot explain. You
> don't have access to a PC with a CAN interface or an oscilloscope, do you?
My PC has our USB-CAN-Modules attached (single or dual channel), so what do you want to see? a candump log?
My access to oscilloscopes rather limited and not reliable.
Best regards,
Alexander
--
Dipl.-Inf. Alexander Stein
SYS TEC electronic GmbH
Am Windrad 2
08468 Heinsdorfergrund
Tel.: 03765 38600-1156
Fax: 03765 38600-4100
Email: alexander.stein@systec-electronic.com
Website: www.systec-electronic.com
Managing Director: Dipl.-Phys. Siegmar Schmidt
Commercial registry: Amtsgericht Chemnitz, HRB 28082
next prev parent reply other threads:[~2014-10-06 14:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 9:41 [RESEND] [PATCH] net: CAN: at91_can.c: decrease likelyhood of RX overruns David Jander
2014-10-02 12:41 ` Alexander Stein
2014-10-03 9:01 ` David Jander
2014-10-06 8:52 ` Alexander Stein
2014-10-06 9:26 ` David Jander
2014-10-06 11:21 ` Alexander Stein
2014-10-06 11:39 ` David Jander
2014-10-06 12:52 ` Marc Kleine-Budde
2014-10-06 14:14 ` Alexander Stein [this message]
2014-10-07 8:31 ` David Jander
2014-10-07 11:36 ` Alexander Stein
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=3545685.3jS4Whu5tJ@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=david@protonic.nl \
--cc=hjk@hansjkoch.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 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.