From: subashab@codeaurora.org
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: rps: fix data stall after hotplug
Date: Tue, 31 Mar 2015 22:02:03 -0000 [thread overview]
Message-ID: <667cd94f1b58cc008ddcb91751f90fd7.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <1427777316.25985.168.camel@edumazet-glaptop2.roam.corp.google.com>
> Listen, I would rather disable RPS on your arch, instead of messing with
> it.
>
> Reset NAPI state as you did is in direct violation of the rules.
>
> Only cpu owning the bit is allowed to reset it.
>
Perhaps my understanding of the code in dev_cpu_callback() is incorrect?
Please correct me if I am wrong.
The poll list is copied from an offline cpu to an online cpu.
Specifically for process_backlog, I was under the impression that
the online cpu tries to reset the state of NAPI of the offline cpu.
The process and input queues are then always copied to the
online cpu.
while (!list_empty(&oldsd->poll_list)) {
struct napi_struct *napi = list_first_entry(&oldsd->poll_list,
struct napi_struct,
poll_list);
list_del_init(&napi->poll_list);
if (napi->poll == process_backlog)
napi->state = 0;
else
____napi_schedule(sd, napi);
}
My request was to know why it would be incorrect to clear the offline cpu
backlog NAPI state unconditionally.
next prev parent reply other threads:[~2015-03-31 22:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 19:54 [PATCH] net: rps: fix data stall after hotplug subashab
2015-03-19 21:50 ` Eric Dumazet
2015-03-20 11:50 ` Eric Dumazet
2015-03-20 16:40 ` subashab
2015-03-23 22:16 ` subashab
2015-03-23 22:29 ` Eric Dumazet
2015-03-25 18:54 ` subashab
2015-03-30 23:49 ` subashab
2015-03-31 4:48 ` Eric Dumazet
2015-03-31 22:02 ` subashab [this message]
2015-03-31 23:44 ` Eric Dumazet
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=667cd94f1b58cc008ddcb91751f90fd7.squirrel@www.codeaurora.org \
--to=subashab@codeaurora.org \
--cc=eric.dumazet@gmail.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).