mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Pargmann <mpa@pengutronix.de>
To: Joe Perches <joe@perches.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
	Wolfgang Grandegger <wg@grandegger.com>,
	linux-can@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] can: c_can: Speed up rx_poll function
Date: Mon, 28 Oct 2013 19:28:18 +0100	[thread overview]
Message-ID: <20131028182818.GB20839@pengutronix.de> (raw)
In-Reply-To: <1382980336.30941.40.camel@joe-AO722>

On Mon, Oct 28, 2013 at 10:12:16AM -0700, Joe Perches wrote:
> On Mon, 2013-10-28 at 17:59 +0100, Markus Pargmann wrote:
> > This patch speeds up the rx_poll function by reducing the number of
> > register reads.
> 
> trivial notes:
> 
> > diff --git a/drivers/net/can/c_can/c_can.c b/drivers/net/can/c_can/c_can.c
> []
> > @@ -259,6 +259,12 @@ static u32 c_can_read_reg32(struct c_can_priv *priv, enum reg index)
> > +u16 c_can_read_reg16(struct c_can_priv *priv, enum reg index)
> > +{
> > +	u16 val = priv->read_reg(priv, index);
> > +	return val;
> > +}
> 
> This function doesn't seem useful at all.
> It's not exported and it's not static.

Oh right, should be static.

> 
> Why not use an in-place priv->read_reg(priv, index)?

No reason for that. Especially with a u16 as mentioned below, it is
clear enough that we have a 16bit value, so I will change it.

> 
> > +
> >  static void c_can_enable_all_interrupts(struct c_can_priv *priv,
> >  						int enable)
> >  {
> > @@ -798,17 +804,21 @@ 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);
> > +	unsigned long val = c_can_read_reg16(priv, C_CAN_INTPND1_REG);
> 
> Probably better as a u16 as detailed below.
> 
> > +	/*
> > +	 * 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 = c_can_read_reg16(priv, C_CAN_INTPND1_REG))) {
> > +		msg_obj = 0;
> > +		while ((msg_obj = find_next_bit(&val, 16, msg_obj)) < 16 &&
> 
> Using ffs instead of find_next_bit would be more standard
> and probably faster too.

I wasn't aware of that. I will change it

Thanks,

Markus Pargmann

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

      reply	other threads:[~2013-10-28 18:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 16:59 Markus Pargmann
2013-10-28 17:12 ` Joe Perches
2013-10-28 18:28   ` Markus Pargmann [this message]

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=20131028182818.GB20839@pengutronix.de \
    --to=mpa@pengutronix.de \
    --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=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: 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

all inboxes | Powered by JetHome®