From: Ido Schimmel <idosch@idosch.org>
To: Li RongQing <lirongqing@baidu.com>
Cc: netdev@vger.kernel.org, idosch@mellanox.com
Subject: Re: [PATCH][net-next] net: drop_monitor: change the stats variable to u64 in net_dm_stats_put
Date: Thu, 22 Aug 2019 14:59:46 +0300 [thread overview]
Message-ID: <20190822115946.GA25090@splinter> (raw)
In-Reply-To: <1566454953-29321-1-git-send-email-lirongqing@baidu.com>
On Thu, Aug 22, 2019 at 02:22:33PM +0800, Li RongQing wrote:
> only the element drop of struct net_dm_stats is used, so simplify it to u64
Thanks for the patch, but I don't really see the value here. The struct
allows for easy extensions in the future. What do you gain from this
change? We merely read stats and report them to user space, so I guess
it's not about performance either.
>
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> ---
> net/core/drop_monitor.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/net/core/drop_monitor.c b/net/core/drop_monitor.c
> index bfc024024aa3..ed10a40cf629 100644
> --- a/net/core/drop_monitor.c
> +++ b/net/core/drop_monitor.c
> @@ -1329,11 +1329,11 @@ static int net_dm_cmd_config_get(struct sk_buff *skb, struct genl_info *info)
> return rc;
> }
>
> -static void net_dm_stats_read(struct net_dm_stats *stats)
> +static void net_dm_stats_read(u64 *stats)
> {
> int cpu;
>
> - memset(stats, 0, sizeof(*stats));
> + *stats = 0;
> for_each_possible_cpu(cpu) {
> struct per_cpu_dm_data *data = &per_cpu(dm_cpu_data, cpu);
> struct net_dm_stats *cpu_stats = &data->stats;
> @@ -1345,14 +1345,14 @@ static void net_dm_stats_read(struct net_dm_stats *stats)
> dropped = cpu_stats->dropped;
> } while (u64_stats_fetch_retry_irq(&cpu_stats->syncp, start));
>
> - stats->dropped += dropped;
> + *stats += dropped;
> }
> }
>
> static int net_dm_stats_put(struct sk_buff *msg)
> {
> - struct net_dm_stats stats;
> struct nlattr *attr;
> + u64 stats;
>
> net_dm_stats_read(&stats);
>
> @@ -1361,7 +1361,7 @@ static int net_dm_stats_put(struct sk_buff *msg)
> return -EMSGSIZE;
>
> if (nla_put_u64_64bit(msg, NET_DM_ATTR_STATS_DROPPED,
> - stats.dropped, NET_DM_ATTR_PAD))
> + stats, NET_DM_ATTR_PAD))
> goto nla_put_failure;
>
> nla_nest_end(msg, attr);
> --
> 2.16.2
>
next prev parent reply other threads:[~2019-08-22 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 6:22 [PATCH][net-next] net: drop_monitor: change the stats variable to u64 in net_dm_stats_put Li RongQing
2019-08-22 11:59 ` Ido Schimmel [this message]
2019-08-22 12:31 ` 答复: " Li,Rongqing
2019-08-29 13:45 ` David Laight
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=20190822115946.GA25090@splinter \
--to=idosch@idosch.org \
--cc=idosch@mellanox.com \
--cc=lirongqing@baidu.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).