From: David Miller <davem@davemloft.net>
To: gfree.wind@vip.163.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: rfs: Don't reset RFS entries when nothing changed
Date: Mon, 22 May 2017 23:02:20 -0400 (EDT) [thread overview]
Message-ID: <20170522.230220.402998640470537222.davem@davemloft.net> (raw)
In-Reply-To: <1495500311-81095-1-git-send-email-gfree.wind@vip.163.com>
From: gfree.wind@vip.163.com
Date: Tue, 23 May 2017 08:45:11 +0800
> From: Gao Feng <gfree.wind@vip.163.com>
>
> When the new RFS table size specified by sysctl equals the old one,
> there is nothing changed actually. So it is unnecessary to reset the
> RFS table entris.
>
> Signed-off-by: Gao Feng <gfree.wind@vip.163.com>
It seems like an intentional feature to be able to reset the
table by simply writing the same value to the sysfs knob.
I'm not applying this, sorry.
next prev parent reply other threads:[~2017-05-23 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 0:45 [PATCH net-next] net: rfs: Don't reset RFS entries when nothing changed gfree.wind
2017-05-23 3:02 ` David Miller [this message]
2017-05-23 3:10 ` 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=20170522.230220.402998640470537222.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;
as well as URLs for NNTP newsgroup(s).