From: Dario Binacchi <dariobin@libero.it>
To: linux-kernel@vger.kernel.org
Cc: Gianluca Falavigna <gianluca.falavigna@inwind.it>,
Dario Binacchi <dariobin@libero.it>, Andrew Lunn <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Oliver Hartkopp <socketcan@hartkopp.net>,
Tong Zhang <ztong0001@gmail.com>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Wolfgang Grandegger <wg@grandegger.com>,
linux-can@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH v2 0/4] can: c_can: cache frames to operate as a true FIFO
Date: Thu, 5 Aug 2021 22:18:56 +0200 [thread overview]
Message-ID: <20210805201900.23146-1-dariobin@libero.it> (raw)
Performance tests of the c_can driver led to the patch that gives the
series its name. I also added two patches not really related to the topic
of the series.
Changes in v2:
- Move c_can_get_tx_free() from c_can_main.c to c_can.h.
Dario Binacchi (4):
can: c_can: remove struct c_can_priv::priv field
can: c_can: exit c_can_do_tx() early if no frames have been sent
can: c_can: support tx ring algorithm
can: c_can: cache frames to operate as a true FIFO
drivers/net/can/c_can/c_can.h | 26 ++++++-
drivers/net/can/c_can/c_can_main.c | 100 +++++++++++++++++++------
drivers/net/can/c_can/c_can_platform.c | 1 -
3 files changed, 101 insertions(+), 26 deletions(-)
--
2.17.1
next reply other threads:[~2021-08-05 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 20:18 Dario Binacchi [this message]
2021-08-05 20:18 ` [PATCH v2 1/4] can: c_can: remove struct c_can_priv::priv field Dario Binacchi
2021-08-05 20:18 ` [PATCH v2 2/4] can: c_can: exit c_can_do_tx() early if no frames have been sent Dario Binacchi
2021-08-05 20:18 ` [PATCH v2 3/4] can: c_can: support tx ring algorithm Dario Binacchi
2021-08-05 20:19 ` [PATCH v2 4/4] can: c_can: cache frames to operate as a true FIFO Dario Binacchi
2021-08-06 9:36 ` 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=20210805201900.23146-1-dariobin@libero.it \
--to=dariobin@libero.it \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=gianluca.falavigna@inwind.it \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=wg@grandegger.com \
--cc=ztong0001@gmail.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.