Netdev List
 help / color / mirror / Atom feed
From: Michael Riesch <michael@riesch.at>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>
Subject: usbnet with NAPI
Date: Fri, 15 Apr 2011 15:05:35 +0200	[thread overview]
Message-ID: <20110415150535.15885rkpiuobevks@webmail.df.eu> (raw)

Habidere,

it looks like the usbnet (on which asix.c bases -> I am still working  
on the driver for the Asix AX88172A[1]) does not use NAPI. It  
processes the data it receives via netif_rx(). The NAPI way would be  
netif_receive_skb in a poll function. Now I would like to check  
whether the incoming packets are PTP status frames. My problem is that  
skb_defer_rx_timestamp (the PTP check is executed there -  
net/core/timestamping.c) is called by netif_receive_skb, but it is not  
called by netif_rx(). So the crude hack would be to call  
skb_defer_rx_timestamp from the netif_rx() in usbnet.

(It caused the whole system to hang after a few minutes of operation,  
so I declared it crude. Haven't found the exact reason for this  
behaviour, though...)

The nicer way would probably be enabling usbnet to use NAPI. Now:

- Is or was there some thinking about usbnet going NAPI? In case of  
the latter, what was the reason that it was not done? (I could not  
find any discussion about that topic)

- Do you see problems doing so? I have read some documentation about  
NAPI [2], the requirements seem to be a DMA ring and the ability to  
turn off interrupts/events that send packets up the stack.

- Who is going to maintain usbnet in the future?

Looking forward to your comments/ideas,
Michael

[1] http://marc.info/?l=linux-netdev&m=130167000017199&w=2
[2] http://www.linuxfoundation.org/collaborate/workgroups/networking/napi



                 reply	other threads:[~2011-04-15 13:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110415150535.15885rkpiuobevks@webmail.df.eu \
    --to=michael@riesch.at \
    --cc=davem@davemloft.net \
    --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