From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC PATCH] openvswitch: use percpu flow stats
Date: Fri, 19 Aug 2016 18:09:53 -0700 (PDT) [thread overview]
Message-ID: <20160819.180953.970774471141286228.davem@davemloft.net> (raw)
In-Reply-To: <1471636616.29842.110.camel-XN9IlZ5yJG9HTL0Zs8A6p+yfmBU6pStAUsxypvmhUTTZJqsBc5GL+g@public.gmane.org>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 19 Aug 2016 12:56:56 -0700
> On Fri, 2016-08-19 at 16:47 -0300, Thadeu Lima de Souza Cascardo wrote:
>> Instead of using flow stats per NUMA node, use it per CPU. When using
>> megaflows, the stats lock can be a bottleneck in scalability.
>
> ...
>
>>
>> flow_cache = kmem_cache_create("sw_flow", sizeof(struct sw_flow)
>> - + (nr_node_ids
>> + + (num_possible_cpus()
>> * sizeof(struct flow_stats *)),
>> 0, 0, NULL);
>> if (flow_cache == NULL)
>
> This is bogus.
>
> Please use nr_cpu_ids instead of num_possible_cpus().
Then how would hot-plugged cpus be handled properly?
The only other way is you'd have to free all objects in the current
flow_cache, destroy it, then make a new kmem_cache and reallocate
all of the existing objects and hook them back up every time a cpu
up event occurs.
That doesn't make any sense at all.
Therefore, the size of the objects coming out of "sw_flow" have
to accomodate all possible cpu indexes.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
next prev parent reply other threads:[~2016-08-20 1:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 19:47 [RFC PATCH] openvswitch: use percpu flow stats Thadeu Lima de Souza Cascardo
[not found] ` <1471636046-9246-1-git-send-email-cascardo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-08-19 19:56 ` Eric Dumazet
[not found] ` <1471636616.29842.110.camel-XN9IlZ5yJG9HTL0Zs8A6p+yfmBU6pStAUsxypvmhUTTZJqsBc5GL+g@public.gmane.org>
2016-08-20 1:09 ` David Miller [this message]
[not found] ` <20160819.180953.970774471141286228.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2016-08-20 4:07 ` Eric Dumazet
2016-08-20 5:25 ` David Miller
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=20160819.180953.970774471141286228.davem@davemloft.net \
--to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
--cc=dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org \
--cc=eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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