From: David Miller <davem@davemloft.net>
To: gfree.wind@vip.163.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: rps: Add the rfs_needed check when record flow hash
Date: Thu, 25 May 2017 13:11:41 -0400 (EDT) [thread overview]
Message-ID: <20170525.131141.1106125565617394205.davem@davemloft.net> (raw)
In-Reply-To: <1495611359-118199-1-git-send-email-gfree.wind@vip.163.com>
From: gfree.wind@vip.163.com
Date: Wed, 24 May 2017 15:35:59 +0800
>
> +static inline void sock_rps_record_flow_hash(__u32 hash)
> +{
> +#ifdef CONFIG_RPS
> + if (static_key_false(&rfs_needed))
> + _sock_rps_record_flow_hash(hash);
> +#endif
> +}
> +
This is no longer used.
If you have some plans to use it in another context, you absolutely _MUST_
post this change inside of a patch series that adds the new user as well.
Otherwise it is impossible to determine the correctness and
appropriateness of your changes.
Thanks.
next prev parent reply other threads:[~2017-05-25 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 7:35 [PATCH net-next] net: rps: Add the rfs_needed check when record flow hash gfree.wind
2017-05-25 14:55 ` Eric Dumazet
2017-05-25 17:11 ` David Miller [this message]
2017-05-26 0:32 ` 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=20170525.131141.1106125565617394205.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gfree.wind@vip.163.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