Netdev Archive on lore.kernel.org help / color / mirror / Atom feed
From: Andrejs Cainikovs <Andrejs.Cainikovs@netmodule.com> To: Wolfgang Grandegger <wg@grandegger.com>, Marc Kleine-Budde <mkl@pengutronix.de>, "David S . Miller" <davem@davemloft.net>, "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>, "netdev@vger.kernel.org" <netdev@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org> Cc: Patrick Zysset <Patrick.Zysset@netmodule.com> Subject: [PATCH 0/2] D_CAN RX buffer size improvements Date: Fri, 8 Feb 2019 13:31:00 +0000 [thread overview] Message-ID: <20190208132954.28166-1-andrejs.cainikovs@netmodule.com> (raw) Re-sending entire patchset due to missed cover letter, sorry. This patchset introduces support for 64 D_CAN message objects with an option of unequal split between RX/TX. The rationale behind this is that there are lots of frame loss on higher bus speeds. Below are test results from my custom Sitara AM3352 based board: Sender: timeout 15m cangen can0 -g 0 -i x Target: candump can0,0~0,#FFFFFFFF -td -c -d -e * Without patches: - 15 minute RX test, 500kbps - 16 RX / 16 TX message objects - 77 received frames lost out of 4649415 * With patches applied: - 15 hours RX test, 500kbps - 56 RX / 8 TX message objects - 41 received frames lost out of 279303376 Please note, I do not have ability to test pure C_CAN, so it is left untested. --- Andrejs Cainikovs (2): can: c_can: support 64 message objects for D_CAN can: c_can: configurable amount of D_CAN RX objects drivers/net/can/c_can/Kconfig | 20 ++++++++++ drivers/net/can/c_can/c_can.c | 93 +++++++++++++++++++++++++++---------------- drivers/net/can/c_can/c_can.h | 20 +++++++--- 3 files changed, 94 insertions(+), 39 deletions(-) --- 2.11.0
next reply other threads:[~2019-02-08 13:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-08 13:31 Andrejs Cainikovs [this message] 2019-02-08 13:31 ` [PATCH 1/2] can: c_can: support 64 message objects for D_CAN Andrejs Cainikovs 2019-02-08 13:31 ` [PATCH 2/2] can: c_can: configurable amount of D_CAN RX objects Andrejs Cainikovs 2021-01-13 18:43 ` [PATCH 0/2] D_CAN RX buffer size improvements Ezequiel Garcia 2021-08-06 10:16 ` Andrejs Cainikovs 2021-08-06 10:36 ` Marc Kleine-Budde 2021-08-06 13:53 ` Ezequiel Garcia
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=20190208132954.28166-1-andrejs.cainikovs@netmodule.com \ --to=andrejs.cainikovs@netmodule.com \ --cc=Patrick.Zysset@netmodule.com \ --cc=davem@davemloft.net \ --cc=linux-can@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mkl@pengutronix.de \ --cc=netdev@vger.kernel.org \ --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: linkBe 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).