From: Shaokun Zhang <zhangshaokun@hisilicon.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<jinyuqi@huawei.com>, <kuznet@ms2.inr.ac.ru>,
<yoshfuji@linux-ipv6.org>, <edumazet@google.com>,
<guoyang2@huawei.com>, Will Deacon <will@kernel.org>
Subject: Re: [PATCH] net: optimize cmpxchg in ip_idents_reserve
Date: Fri, 17 Jan 2020 14:54:03 +0800 [thread overview]
Message-ID: <430496fc-9f26-8cb4-91d8-505fda9af230@hisilicon.com> (raw)
In-Reply-To: <1b3aaddf-22f5-1846-90f1-42e68583c1e4@gmail.com>
+Cc Will Deacon,
On 2020/1/16 23:19, Eric Dumazet wrote:
>
>
> On 1/16/20 7:12 AM, Eric Dumazet wrote:
>>
>>
>> On 1/16/20 4:27 AM, David Miller wrote:
>>> From: Shaokun Zhang <zhangshaokun@hisilicon.com>
>>> Date: Wed, 15 Jan 2020 11:23:40 +0800
>>>
>>>> From: Yuqi Jin <jinyuqi@huawei.com>
>>>>
>>>> atomic_try_cmpxchg is called instead of atomic_cmpxchg that can reduce
>>>> the access number of the global variable @p_id in the loop. Let's
>>>> optimize it for performance.
>>>>
>>>> Cc: "David S. Miller" <davem@davemloft.net>
>>>> Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
>>>> Cc: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
>>>> Cc: Eric Dumazet <edumazet@google.com>
>>>> Cc: Yang Guo <guoyang2@huawei.com>
>>>> Signed-off-by: Yuqi Jin <jinyuqi@huawei.com>
>>>> Signed-off-by: Shaokun Zhang <zhangshaokun@hisilicon.com>
>>>
>>> I doubt this makes any measurable improvement in performance.
>>>
>>> If you can document a specific measurable improvement under
>>> a useful set of circumstances for real usage, then put those
>>> details into the commit message and resubmit.
>>>
>>> Otherwise, I'm not applying this, sorry.
>>>
>>
>>
>> Real difference that could be made here is to
>> only use this cmpxchg() dance for CONFIG_UBSAN
>>
>> When CONFIG_UBSAN is not set, atomic_add_return() is just fine.
>>
>> (Supposedly UBSAN should not warn about that either, but this depends on compiler version)
>
> I will test something like :
>
> diff --git a/net/ipv4/route.c b/net/ipv4/route.c
> index 2010888e68ca96ae880481973a6d808d6c5612c5..e2fa972f5c78f2aefc801db6a45b2a81141c3028 100644
> --- a/net/ipv4/route.c
> +++ b/net/ipv4/route.c
> @@ -495,11 +495,15 @@ u32 ip_idents_reserve(u32 hash, int segs)
> if (old != now && cmpxchg(p_tstamp, old, now) == old)
> delta = prandom_u32_max(now - old);
>
> - /* Do not use atomic_add_return() as it makes UBSAN unhappy */
> +#ifdef CONFIG_UBSAN
I appreciate Eric's idea.
> + /* Do not use atomic_add_return() as it makes old UBSAN versions unhappy */
> do {
> old = (u32)atomic_read(p_id);
> new = old + delta + segs;
> } while (atomic_cmpxchg(p_id, old, new) != old);
But about this, I still think that we can try to use atomic_try_cmpxchg instead
of atomic_cmpxchg, like refcount_add_not_zero in include/linux/refcount.h
I abstract the model, as follow:
while (get_cycles() <= (time_temp + t_cnt))
{
do{
old_temp = wk_in->num.counter;
oldt = atomic64_cmpxchg(&wk_in->num, old_temp, old_temp+1);
}while(oldt != old_temp);
myndelay(delay_o);
w_cnt+=1;
}
val = atomic64_read(&wk_in->num);
while (get_cycles() <= (time_temp + t_cnt))
{
do{
new_val = val + 1;
}while(!atomic64_try_cmpxchg(&wk_in->num, &val, new_val));
myndelay(delay_o);
w_cnt += 1;
}
If we take the access global variable out of loop, the performance become better
on both x86 and arm64, as follow:
Kunpeng920: 24 cores call it and the successful operations per second
atomic64_read in loop atomic64_read out of the loop
6291034 8751962
Intel 6248: 20 cores call it and the successful operations per second
atomic64_read in loop atomic64_read out of the loop
8934792 9978998
So how about this? ;-)
delta = prandom_u32_max(now - old);
+#ifdef CONFIG_UBSAN
/* Do not use atomic_add_return() as it makes UBSAN unhappy */
+ old = (u32)atomic_read(p_id);
do {
- old = (u32)atomic_read(p_id);
new = old + delta + segs;
- } while (atomic_cmpxchg(p_id, old, new) != old);
+ } while (!atomic_try_cmpxchg(p_id, &old, new));
+#else
+ new = atomic_add_return(segs + delta, p_id);
+#endif
Thanks,
Shaokun
> +#else
> + new = atomic_add_return(segs + delta, p_id);
> +#endif
>
> return new - segs;
> }
>
>
> .
>
next prev parent reply other threads:[~2020-01-17 6:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 3:23 Shaokun Zhang
2020-01-16 12:27 ` David Miller
2020-01-16 14:05 ` Shaokun Zhang
2020-01-16 15:12 ` Eric Dumazet
2020-01-16 15:19 ` Eric Dumazet
2020-01-17 6:54 ` Shaokun Zhang [this message]
2020-01-17 12:32 ` Peter Zijlstra
2020-01-17 16:35 ` Eric Dumazet
2020-01-17 18:03 ` Arvind Sankar
2020-01-17 18:16 ` Eric Dumazet
2020-01-17 18:38 ` Arvind Sankar
2020-01-17 18:48 ` Eric Dumazet
2020-01-20 8:18 ` Peter Zijlstra
2020-05-07 9:12 ` Shaokun Zhang
2020-05-07 13:49 ` Eric Dumazet
2020-01-19 3:46 ` Shaokun Zhang
2020-01-19 4:12 ` Eric Dumazet
2020-01-21 2:40 ` Shaokun Zhang
2020-01-22 8:49 ` Peter Zijlstra
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=430496fc-9f26-8cb4-91d8-505fda9af230@hisilicon.com \
--to=zhangshaokun@hisilicon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=guoyang2@huawei.com \
--cc=jinyuqi@huawei.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=will@kernel.org \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®