linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nvishwan@codeaurora.org (nvishwan at codeaurora.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] msm: rmnet: msm rmnet smd virtual ethernet driver
Date: Tue, 21 Dec 2010 15:45:45 -0800 (PST)	[thread overview]
Message-ID: <2c27ccc1dd4db9a31cd961f0ffaed886.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <20101215134406.3a634aa8@nehalam>

> On Wed, 15 Dec 2010 10:31:06 -0800
> Niranjana Vishwanathapura <nvishwan@codeaurora.org> wrote:
>
>> +
>> +static DECLARE_TASKLET(smd_net_data_tasklet, smd_net_data_handler, 0);
>> +
>> +static void smd_net_notify(void *_dev, unsigned event)
>> +{
>> +	if (event != SMD_EVENT_DATA)
>> +		return;
>> +
>> +	smd_net_data_tasklet.data = (unsigned long) _dev;
>> +
>> +	tasklet_schedule(&smd_net_data_tasklet);
>> +}
>> +
>
> Rather than having private tasklet, maybe using NAPI
> would be better?
>
> Also since you are already in tasklet, no need to call netif_rx()
> when receiving packet; instead use netif_receive_skb directly.
>
> --
>

NAPI will not buy much as the SMD transport doesn't provide a machanism to
stop interrupts.  I will consider using NAPI in the future (it requires
performance testing on lot of different targets).

However, I can replace netif_rx() by netif_receive_skb() and send out new
patch

      reply	other threads:[~2010-12-21 23:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 18:31 [PATCH] msm: rmnet: msm rmnet smd virtual ethernet driver Niranjana Vishwanathapura
2010-12-15 21:04 ` Arnd Bergmann
2010-12-21 23:44   ` nvishwan at codeaurora.org
2010-12-15 21:41 ` Stephen Hemminger
2010-12-21 23:44   ` nvishwan at codeaurora.org
2010-12-15 21:41 ` Stephen Hemminger
2010-12-21 23:45   ` nvishwan at codeaurora.org
2010-12-15 21:44 ` Stephen Hemminger
2010-12-21 23:45   ` nvishwan at codeaurora.org [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=2c27ccc1dd4db9a31cd961f0ffaed886.squirrel@www.codeaurora.org \
    --to=nvishwan@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).