From: "Gao Feng" <gfree.wind@vip.163.com>
To: "Eric Dumazet" <eric.dumazet@gmail.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
daniel@iogearbox.net, jakub.kicinski@netronome.com,
"David Ahern" <dsahern@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re:Re: [PATCH net] net: Correct wrong skb_flow_limit check when enable RPS
Date: Fri, 11 May 2018 08:18:30 +0800 (CST) [thread overview]
Message-ID: <654af0ff.3e1.1634c90380e.Coremail.gfree.wind@vip.163.com> (raw)
In-Reply-To: <5ac360c4-0936-9c12-56cb-f81f08c925e6@gmail.com>
At 2018-05-10 21:02:55, "Eric Dumazet" <eric.dumazet@gmail.com> wrote:
>
>
>On 05/10/2018 01:28 AM, gfree.wind@vip.163.com wrote:
>> From: Gao Feng <gfree.wind@vip.163.com>
>>
>> The skb flow limit is implemented for each CPU independently. In the
>> current codes, the function skb_flow_limit gets the softnet_data by
>> this_cpu_ptr. But the target cpu of enqueue_to_backlog would be not
>> the current cpu when enable RPS. As the result, the skb_flow_limit checks
>> the stats of current CPU, while the skb is going to append the queue of
>> another CPU. It isn't the expected behavior.
>>
>> Now pass the softnet_data as a param to softnet_data to make consistent.
>>
>
>Please add a correct Fixes: tag
Thanks Eric.
I have one question about the "Fixes: tag".
Most of patches are bug fixes, but when need to add the "Fixes: tag", and when not ?
I'm not clear about it. Could you explain it please?
Best Regards
Feng
>
>By doing so, you will likely add a CC: tag to make sure the author of the code
>will receive your email and give feed back.
>
>Thanks !
>
next prev parent reply other threads:[~2018-05-11 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 8:28 [PATCH net] net: Correct wrong skb_flow_limit check when enable RPS gfree.wind
2018-05-10 13:02 ` Eric Dumazet
2018-05-11 0:18 ` Gao Feng [this message]
2018-05-11 0:55 ` Eric Dumazet
2018-05-11 1:29 ` Gao Feng
2018-05-11 3:54 ` Willem de Bruijn
2018-05-11 6:20 ` Gao Feng
2018-05-11 13:23 ` Willem de Bruijn
2018-05-11 14:44 ` Gao Feng
2018-05-11 14:56 ` Willem de Bruijn
2018-05-14 1:26 ` Gao Feng
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=654af0ff.3e1.1634c90380e.Coremail.gfree.wind@vip.163.com \
--to=gfree.wind@vip.163.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=jakub.kicinski@netronome.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