[<prev] [next>] [day] [month] [year] [list]
Message-ID: <42c422c6cc99497586a4a678dfe8ba34@huawei.com>
Date: Thu, 5 Jun 2025 13:43:46 +0000
From: mengkanglai <mengkanglai2@...wei.com>
To: "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
<pabeni@...hat.com>, Simon Horman <horms@...nel.org>, Kuniyuki Iwashima
<kuniyu@...zon.com>, Stanislav Fomichev <stfomichev@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "Yanan (Euler)" <yanan@...wei.com>, "Fengtao (fengtao, Euler)"
<fengtao40@...wei.com>
Subject: skb defer free casues a lot of memory not released in hugepages
Hello:
In my virtualization scenario, physical host enable hugepages feature and share hugepages to the virtual machine running on it.
A large amount of data is exchanged between the host and the vm through TCP local communication.Later, the vm is no longer needed and is destroyed, but the hugepages shared to the vm was not fully released back to the host.
Tracing showed that the hugepages are occupied by skbs in host due to commit 68822bdf76f10 ("net: generalize skb freeing deferral to per-cpu lists").
it will remain some skbs in cpu skb_defer_list to defer free, it seems that may cause infinite delay if there is no triggering for net_rx_action().
A large amount of memory is not released because there are many CPUs and hugepages feature. Host can't recycle memory fast enough will affect the subsequent VM hugepages allocation.
Maybe we need a general method to release skb immediately or a timeout mechanism for skbs in defer list to release?
Best wishes!
Powered by blists - more mailing lists