[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230531194520.qhvibyyaqg7vwi6s@google.com>
Date: Wed, 31 May 2023 19:45:20 +0000
From: Shakeel Butt <shakeelb@...gle.com>
To: Oliver Sang <oliver.sang@...el.com>
Cc: Zhang Cathy <cathy.zhang@...el.com>, Yin Fengwei <fengwei.yin@...el.com>,
Feng Tang <feng.tang@...el.com>, Eric Dumazet <edumazet@...gle.com>, Linux MM <linux-mm@...ck.org>,
Cgroups <cgroups@...r.kernel.org>, Paolo Abeni <pabeni@...hat.com>,
"davem@...emloft.net" <davem@...emloft.net>, "kuba@...nel.org" <kuba@...nel.org>,
Brandeburg Jesse <jesse.brandeburg@...el.com>, Srinivas Suresh <suresh.srinivas@...el.com>,
Chen Tim C <tim.c.chen@...el.com>, You Lizhen <lizhen.you@...el.com>,
"eric.dumazet@...il.com" <eric.dumazet@...il.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, philip.li@...el.com,
yujie.liu@...el.com
Subject: Re: [PATCH net-next 1/2] net: Keep sk->sk_forward_alloc as a proper size
Hi Oliver,
On Wed, May 31, 2023 at 04:46:08PM +0800, Oliver Sang wrote:
[...]
>
> we applied below patch upon v6.4-rc2, so far, we didn't spot out performance
> impacts of it to other tests.
>
> but we found -7.6% regression of netperf.Throughput_Mbps
>
Thanks, this is what I was looking for. I will dig deeper and decide how
to proceed (i.e. improve this patch or work on long term approach).
Powered by blists - more mailing lists