From: Jeff Garzik <jgarzik@pobox.com>
To: Jason Lunz <lunz@falooley.org>
Cc: netdev@oss.sgi.com
Subject: Re: Where is netif_rx() not safe to use?
Date: Mon, 12 May 2003 11:44:34 -0400 [thread overview]
Message-ID: <20030512154434.GD27111@gtf.org> (raw)
In-Reply-To: <slrnbbveq6.321.lunz@stoli.localnet>
On Mon, May 12, 2003 at 03:16:55PM +0000, Jason Lunz wrote:
> jgarzik@pobox.com said:
> >> I'd like to know if there are situations where netif_rx() is not safe to use.
> >> For example, is it safe to call from a timer or from dev->poll()?
> >
> > Sure, that's fine.
>
> from dev->poll()? It could work, but that's abusing the napi design.
> netif_rx() is for non-napi drivers. If a dev has a ->poll() method, it
> should use netif_receive_skb().
agreed.
Jeff
next prev parent reply other threads:[~2003-05-12 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3ebfa567b38e59.35614148@not right>
2003-05-12 14:59 ` Where is netif_rx() not safe to use? Jeff Garzik
2003-05-12 15:16 ` Jason Lunz
2003-05-12 15:44 ` Jeff Garzik [this message]
2003-05-12 13:45 Rask Ingemann Lambertsen
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=20030512154434.GD27111@gtf.org \
--to=jgarzik@pobox.com \
--cc=lunz@falooley.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).