From: Jarek Poplawski <jarkao2@gmail.com>
To: Tom Herbert <therbert@google.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] rps: core implementation
Date: Thu, 19 Nov 2009 08:08:31 +0000 [thread overview]
Message-ID: <20091119080831.GA6874@ff.dom.local> (raw)
In-Reply-To: <65634d660911160843j3df398f2w876044083181cfcd@mail.gmail.com>
On 16-11-2009 17:43, Tom Herbert wrote:
> On Mon, Nov 16, 2009 at 3:19 AM, David Miller <davem@davemloft.net> wrote:
>> From: Tom Herbert <therbert@google.com>
>> Date: Tue, 10 Nov 2009 22:53:17 -0800
>>
>>> + /* Schedule NAPI for backlog device */
>>> + if (napi_schedule_prep(&queue->backlog)) {
>>> + if (cpu != smp_processor_id()) {
>>> + cpu_set(cpu,
>>> + get_cpu_var(rps_remote_softirq_cpus));
>>> + __raise_softirq_irqoff(NET_RPS_SOFTIRQ);
>>> + } else
>>> + __napi_schedule(&queue->backlog);
>>> + }
>>> + goto enqueue;
>> {,__}send_remote_softirq() doesn't work? :-)
>>
> NET_RPS_SOFTIRQ is intended to provide coalescing of IPIs.
It seems calling net_rps_action() at the end of net_rx_action() should
do (mostly) the same, at least for napi drivers. And I'm not sure it's
worth to add a new softirq because of non-napis.
Jarek P.
next prev parent reply other threads:[~2009-11-19 8:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 6:53 [PATCH 1/2] rps: core implementation Tom Herbert
2009-11-11 8:20 ` Eric Dumazet
2009-11-11 16:28 ` Tom Herbert
2009-11-11 21:44 ` Andi Kleen
2009-11-12 2:32 ` David Miller
2009-11-16 11:15 ` David Miller
2009-11-11 16:49 ` Randy Dunlap
2009-11-11 21:43 ` Andi Kleen
2009-11-16 17:02 ` Tom Herbert
2009-11-19 10:08 ` Andi Kleen
2009-11-20 6:41 ` Tom Herbert
2009-11-20 6:49 ` Eric Dumazet
2009-11-12 20:23 ` Eric Dumazet
2009-11-16 11:19 ` David Miller
2009-11-16 16:43 ` Tom Herbert
2009-11-18 7:21 ` David Miller
2009-11-19 8:08 ` Jarek Poplawski [this message]
2009-11-20 22:52 ` David Miller
2009-11-17 21:32 ` Jarek Poplawski
2009-11-19 9:57 ` Jarek Poplawski
2009-11-20 17:08 ` Tom Herbert
2009-11-20 19:00 ` Jarek Poplawski
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=20091119080831.GA6874@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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).