public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Brian Baboch <brian.baboch@gmail.com>
Cc: linux-rdma@vger.kernel.org, stable@vger.kernel.org,
	florent.fourcot@wifirst.fr, brian.baboch@wifirst.fr
Subject: Re: Excessive memory usage when infiniband config is enabled
Date: Tue, 7 May 2024 14:27:30 +0300	[thread overview]
Message-ID: <20240507112730.GB78961@unreal> (raw)
In-Reply-To: <2b4f7f6e-9fe5-43a4-b62e-6e42be67d1d9@gmail.com>

On Mon, May 06, 2024 at 05:15:55PM +0200, Brian Baboch wrote:
> Hello,
> 
> 
> We discovered that the CONFIG_INFINIBAND_IRDMA configuration option in the
> linux kernel is causing excessive memory usage on idle mode on specific
> servers like the DELL VEP4600
> (https://www.dell.com/en-us/shop/ipovw/virtual-edge-platform-4600.
> 
> By default we were using Debian's linux-image-6.1.0-13-amd64 which is the
> stable 6.1.55-1 amd64, we then compiled the kernel again with the same
> config file from the stable 6.1.55 tag and had the same problem. We were
> able to resolve the memory problem by removing the `CONFIG_INFINIBAND_IRDMA`
> option from the kernel config.
> 
> The tag used to reproduce the problem is v6.1.55.
> adding the following config `CONFIG_INFINIBAND_IRDMA=m` causes the excessive
> memory usage to go from 1.4Gb to 7Gb.

Hi Brian,

Why do you think that this is a bug?
DELL VEP4600 supports RDMA, so by enabling CONFIG_INFINIBAND_IRDMA, you
compiled RDMA support for Intel NIC.
https://dl.dell.com/topicspdf/vep4600_tech_guide_en-us.pdf

You can unload irdma.ko module and restore memory footprint.

Thanks

  reply	other threads:[~2024-05-07 11:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 15:15 Excessive memory usage when infiniband config is enabled Brian Baboch
2024-05-07 11:27 ` Leon Romanovsky [this message]
2024-05-07 13:15   ` Brian Baboch
2024-05-07 13:32     ` Konstantin Taranov
2024-05-07 15:24       ` Zhu Yanjun
2024-05-07 16:37         ` Jason Gunthorpe
2024-05-08  1:24           ` Saleem, Shiraz
2024-05-13 13:59             ` Brian Baboch

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=20240507112730.GB78961@unreal \
    --to=leon@kernel.org \
    --cc=brian.baboch@gmail.com \
    --cc=brian.baboch@wifirst.fr \
    --cc=florent.fourcot@wifirst.fr \
    --cc=linux-rdma@vger.kernel.org \
    --cc=stable@vger.kernel.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