From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 849C9C7EE2A for ; Wed, 25 Jun 2025 20:25:58 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 3523C6162F; Wed, 25 Jun 2025 20:25:58 +0000 (UTC) X-Virus-Scanned: amavis at osuosl.org Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavis, port 10024) with ESMTP id b8ej2ick0vmu; Wed, 25 Jun 2025 20:25:55 +0000 (UTC) X-Comment: SPF check N/A for local connections - client-ip=140.211.166.142; helo=lists1.osuosl.org; envelope-from=intel-wired-lan-bounces@osuosl.org; receiver= DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 45C1A6162E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=osuosl.org; s=default; t=1750883155; bh=ylxCpTUuN7sOcpqB+lMQrdkoP/CMdeKpEQdi2hpMpHk=; h=Date:From:To:Cc:In-Reply-To:References:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=OW9iuo1XCTm+202fOMNzh1F/O8RCI7KiFlRdZ3d95HnDryQnnuyr7R97/OUShZqQh pU91yFrtXQ3jTtQNvVyfU46dnMjkyEOeH+CkrAtcWGVCQ4WqrbvTYPKuv6X3bbO/fk 0DKU+JjFaRgGL20lzIQ6qosVO8V+mZjXIR97UUNOmPsv8DU4y3HGukGBrY+Dk5F3V9 l+NHtrutWPMQQ1qc10CJf8Y9mh+tpAXvupnJagWDgaNVp5NAQztm2SAw7jlUFKAROp ZSQ1EhnAUQMxXBsahnlNxqf9PEY+yesQuNfRT03MoBliYZEtycgNW1lOg+a3KEkm+B NUKKh1lJAsm4Q== Received: from lists1.osuosl.org (lists1.osuosl.org [140.211.166.142]) by smtp3.osuosl.org (Postfix) with ESMTP id 45C1A6162E; Wed, 25 Jun 2025 20:25:55 +0000 (UTC) Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists1.osuosl.org (Postfix) with ESMTP id 4D000154 for ; Wed, 25 Jun 2025 20:25:53 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 36AE8400FF for ; Wed, 25 Jun 2025 20:25:53 +0000 (UTC) X-Virus-Scanned: amavis at osuosl.org Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavis, port 10024) with ESMTP id U52-NOIRai67 for ; Wed, 25 Jun 2025 20:25:48 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2604:1380:4641:c500::1; helo=dfw.source.kernel.org; envelope-from=kuba@kernel.org; receiver= DMARC-Filter: OpenDMARC Filter v1.4.2 smtp2.osuosl.org 7ED29400A5 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 7ED29400A5 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by smtp2.osuosl.org (Postfix) with ESMTPS id 7ED29400A5 for ; Wed, 25 Jun 2025 20:25:48 +0000 (UTC) Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id E55E45C4239; Wed, 25 Jun 2025 20:23:30 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A31B6C4CEEA; Wed, 25 Jun 2025 20:25:46 +0000 (UTC) Date: Wed, 25 Jun 2025 13:25:45 -0700 From: Jakub Kicinski To: Jaroslav Pulchart Cc: Przemek Kitszel , "intel-wired-lan@lists.osuosl.org" , "Keller, Jacob E" , "Damato, Joe" , "netdev@vger.kernel.org" , "Nguyen, Anthony L" , Michal Swiatkowski , "Czapnik, Lukasz" , "Dumazet, Eric" , "Zaki, Ahmed" , Martin Karsten , Igor Raits , Daniel Secik , Zdenek Pesek Message-ID: <20250625132545.1772c6ab@kernel.org> In-Reply-To: References: <4a061a51-8a6c-42b8-9957-66073b4bc65f@intel.com> <20250415175359.3c6117c9@kernel.org> <20250416064852.39fd4b8f@kernel.org> <20250416171311.30b76ec1@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1750883147; bh=ylxCpTUuN7sOcpqB+lMQrdkoP/CMdeKpEQdi2hpMpHk=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=j2wN1DZD03yG5kovQ3urG3qKoSG7fdnUM01iTOIvpQgmmV1mnIUFEuIoO6pwZd8Fr br/6jjkLQuj1J6OB4nnqwJrD9M8ArNJuYGVfIAGQdu5GNQHbZHp4jaiwyFg7UvB8kw 14+1xPoZZZAKrgIlHzSlGy9OCX2hxaAkprM4VWMdDMRVC9ewvnHh/y/jVn/cxFPo2S 6cXF3abnhLdz5rD/Z3klTpIW5cgyOwgVWN06BLJOkWI9FIbZLLDARp6tZKWJ+Mb+NP yUZfze1cRDizeNmyF+drEb7Qpfnn4C3h3tttlQb64Ptfe8y2VzDBXQs7NqX29YzWRI mASN6oMOrziEQ== X-Mailman-Original-Authentication-Results: smtp2.osuosl.org; dmarc=pass (p=quarantine dis=none) header.from=kernel.org X-Mailman-Original-Authentication-Results: smtp2.osuosl.org; dkim=pass (2048-bit key, unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=j2wN1DZD Subject: Re: [Intel-wired-lan] Increased memory usage on NUMA nodes with ICE driver after upgrade to 6.13.y (regression in commit 492a044508ad) X-BeenThere: intel-wired-lan@osuosl.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Intel Wired Ethernet Linux Kernel Driver Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-wired-lan-bounces@osuosl.org Sender: "Intel-wired-lan" On Wed, 25 Jun 2025 19:51:08 +0200 Jaroslav Pulchart wrote: > Great, please send me a link to the related patch set. I can apply them in > our kernel build and try them ASAP! Sorry if I'm repeating the question - have you tried CONFIG_MEM_ALLOC_PROFILING? Reportedly the overhead in recent kernels=20 is low enough to use it for production workloads. > st 25. 6. 2025 v 16:03 odes=C3=ADlatel Przemek Kitszel < > przemyslaw.kitszel@intel.com> napsal: =20 >=20 > > On 6/25/25 14:17, Jaroslav Pulchart wrote: =20 > > > Hello > > > > > > We are still facing the memory issue with Intel 810 NICs (even on lat= est > > > 6.15.y). > > > > > > Our current stabilization and solution is to move everything to a new > > > INTEL-FREE server and get rid of last Intel sights there (after Intel= 's > > > CPU vulnerabilities fuckups NICs are next step). > > > > > > Any help welcomed, > > > Jaroslav P. > > > > > > =20 > > > > Thank you for urging us, I can understand the frustration. > > > > We have identified some (unrelated) memory leaks, will soon ship fixes. > > And, as there were no clear issue with any commit/version you have > > posted to be a culprit, there is a chance that our random findings could > > help. Anyway going to zero kmemleak reports is good in itself, that is > > a good start. > > > > Will ask my VAL too to increase efforts in this area too.