From: Francois Romieu <romieu@fr.zoreil.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Nicolae Rosia <nicolae.rosia@gmail.com>,
Jaeden Amero <jaeden.amero@ni.com>,
netdev <netdev@vger.kernel.org>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
Josh Cartwright <joshc@ni.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: macb napi strange behavior
Date: Sat, 20 Jun 2015 18:43:32 +0200 [thread overview]
Message-ID: <20150620164332.GA2505@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <CAGVrzcZxPqyp3CDLc-UQejtVg1QVv5OBuGLQNVSrtfG9H1OUnA@mail.gmail.com>
Florian Fainelli <f.fainelli@gmail.com> :
[...]
> Typically, NAPI is used at the receive side of the Ethernet NIC/driver
> to lower the hard/soft interrupt context switch, although there is
> nothing that prevent you to implement a similar scheme for the
> transmit side. Usually, for transmit you will be submitting one packet
> for transmission and get a completion interrupt, so without interrupt
> coalescing (software or hardware) you can end-up with 1 interrupt per
> packet transmitted.
The wording is a bit shy: there is a long standing policy to move
everything to NAPI context (as well as go mostly lockless, etc.).
Any taker to move macb Tx processing to NAPI context or should I consider it ?
--
Ueimor
next prev parent reply other threads:[~2015-06-20 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 16:09 macb napi strange behavior Nicolae Rosia
2015-06-17 18:54 ` Jaeden Amero
2015-06-17 19:00 ` Nicolae Rosia
2015-06-17 20:20 ` Florian Fainelli
2015-06-20 16:43 ` Francois Romieu [this message]
2015-06-22 19:04 ` Nicolae Rosia
2015-06-26 17:50 ` Nicolae Rosia
2015-06-26 23:15 ` Francois Romieu
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=20150620164332.GA2505@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=cyrille.pitchen@atmel.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jaeden.amero@ni.com \
--cc=joshc@ni.com \
--cc=netdev@vger.kernel.org \
--cc=nicolae.rosia@gmail.com \
--cc=nicolas.ferre@atmel.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