From: Wolfgang Grandegger <wg@grandegger.com>
To: Markus Pargmann <mpa@pengutronix.de>,
Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Joe Perches <joe@perches.com>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH v3] can: c_can: Speed up rx_poll function
Date: Sun, 03 Nov 2013 20:20:30 +0100 [thread overview]
Message-ID: <5276A1FE.7040804@grandegger.com> (raw)
In-Reply-To: <1383298596-18385-1-git-send-email-mpa@pengutronix.de>
On 11/01/2013 10:36 AM, Markus Pargmann wrote:
> This patch speeds up the rx_poll function by reducing the number of
> register reads.
>
> Replace the 32bit register read by a 16bit register read. Currently
> the 32bit register read is implemented by using 2 16bit reads. This is
> inefficient as we only use the lower 16bit in rx_poll.
>
> The for loop reads the pending interrupts in every iteration. This
> leads up to 16 reads of pending interrupts. The patch introduces a new
> outer loop to read the pending interrupts as long as 'quota' is above 0.
> This reduces the total number of reads.
>
> The third change is to replace the for-loop by a ffs loop.
>
> Tested on AM335x. I removed all 'static' and 'inline' from c_can.c to
> see the timings for all functions. I used the function tracer with
> trace_stats.
>
> 125kbit:
> Function Hit Time Avg s^2
> -------- --- ---- --- ---
> c_can_do_rx_poll 63960 10168178 us 158.977 us 1493056 us
> With patch:
> c_can_do_rx_poll 63941 3764057 us 58.867 us 776162.2 us
>
> 1Mbit:
> Function Hit Time Avg s^2
> -------- --- ---- --- ---
> c_can_do_rx_poll 69489 30049498 us 432.435 us 9271851 us
> With patch:
> c_can_do_rx_poll 207109 24322185 us 117.436 us 171469047 us
>
> Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
> ---
>
> Notes:
> Changes in v3:
> - Update commit message (measurements and ffs)
>
> Changes in v2:
> - Small changes, find_next_bit -> ffs and other
>
> drivers/net/can/c_can/c_can.c | 22 ++++++++++++----------
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/net/can/c_can/c_can.c b/drivers/net/can/c_can/c_can.c
> index a668cd4..428681e 100644
> --- a/drivers/net/can/c_can/c_can.c
> +++ b/drivers/net/can/c_can/c_can.c
> @@ -798,17 +798,19 @@ static int c_can_do_rx_poll(struct net_device *dev, int quota)
> u32 num_rx_pkts = 0;
> unsigned int msg_obj, msg_ctrl_save;
> struct c_can_priv *priv = netdev_priv(dev);
> - u32 val = c_can_read_reg32(priv, C_CAN_INTPND1_REG);
> + u16 val;
> +
> + /*
> + * It is faster to read only one 16bit register. This is only possible
> + * for a maximum number of 16 objects.
> + */
> + BUILD_BUG_ON_MSG(C_CAN_MSG_OBJ_RX_LAST > 16,
> + "Implementation does not support more message objects than 16");
> +
> + while (quota > 0 && (val = priv->read_reg(priv, C_CAN_INTPND1_REG))) {
> + while ((msg_obj = ffs(val)) && quota > 0) {
> + val &= ~BIT(msg_obj - 1);
IIRC, we should avoid assignment in if/while statements.
Wolfgang.
next prev parent reply other threads:[~2013-11-03 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 9:36 [PATCH v3] can: c_can: Speed up rx_poll function Markus Pargmann
2013-11-03 19:20 ` Wolfgang Grandegger [this message]
2013-11-03 21:05 ` 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=5276A1FE.7040804@grandegger.com \
--to=wg@grandegger.com \
--cc=joe@perches.com \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=mpa@pengutronix.de \
--cc=netdev@vger.kernel.org \
/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