From: Heiner Kallweit <hkallweit1@gmail.com>
To: Edward Cree <ecree@solarflare.com>,
Jesper Dangaard Brouer <brouer@redhat.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: netif_receive_skb_list and interrupts enabled/disabled
Date: Tue, 26 Mar 2019 21:04:09 +0100 [thread overview]
Message-ID: <5c170def-4c09-8da2-e0cd-6fc29881031f@gmail.com> (raw)
A question inspired by 0a25d92c6f4f ("dpaa2-eth: use netif_receive_skb_list"):
kerneldoc of netif_receive_skb_list states that interrupts should be
enabled. When used from NAPI context irqs typically are disabled.
And if the NAPI budget is fully consumed then interrupts don't get enabled
in the same NAPI poll loop. How is this supposed to play together?
Thanks, Heiner
next reply other threads:[~2019-03-26 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 20:04 Heiner Kallweit [this message]
2019-03-27 8:20 ` netif_receive_skb_list and interrupts enabled/disabled Jesper Dangaard Brouer
2019-03-27 18:55 ` Heiner Kallweit
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=5c170def-4c09-8da2-e0cd-6fc29881031f@gmail.com \
--to=hkallweit1@gmail.com \
--cc=brouer@redhat.com \
--cc=ecree@solarflare.com \
--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;
as well as URLs for NNTP newsgroup(s).