linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bharat Agrawal <bharat.agrawal@ansys.com>
To: "hughd@google.com" <hughd@google.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"rientjes@google.com" <rientjes@google.com>,
	"zhangyiru3@huawei.com" <zhangyiru3@huawei.com>,
	"liuzixian4@huawei.com" <liuzixian4@huawei.com>,
	"mhocko@suse.com" <mhocko@suse.com>,
	"wuxu.wu@huawei.com" <wuxu.wu@huawei.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re:  mlock ulimits for SHM_HUGETLB
Date: Mon, 19 May 2025 10:23:33 +0000	[thread overview]
Message-ID: <SJ2PR01MB834515EA00BD7C362A77972F8E9CA@SJ2PR01MB8345.prod.exchangelabs.com> (raw)
In-Reply-To: <SJ2PR01MB8345DF192742AC4DB3D2CBB78E9CA@SJ2PR01MB8345.prod.exchangelabs.com>

Hi all,

Could anyone please help comment on the risks associated with an application throwing the "Using mlock ulimits for SHM_HUGETLB is deprecated" message on RHEL 8.9 with 4.18.0-513.18.1.el8_9.x86_64 Linux kernel?

Best,
Bharat Agrawal
ANSYS, Inc.

  reply	other threads:[~2025-05-19 10:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19 10:21 Bharat Agrawal
2025-05-19 10:23 ` Bharat Agrawal [this message]
2025-05-19 11:32   ` Greg KH
2025-05-19 12:04     ` Bharat Agrawal
2025-05-19 12:05       ` Bharat Agrawal
2025-05-19 12:32       ` Greg KH
2025-05-19 12:41         ` Bharat Agrawal
2025-05-19 12:42           ` Bharat Agrawal
2025-05-19 14:02 ` Michal Hocko

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=SJ2PR01MB834515EA00BD7C362A77972F8E9CA@SJ2PR01MB8345.prod.exchangelabs.com \
    --to=bharat.agrawal@ansys.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liuzixian4@huawei.com \
    --cc=mhocko@suse.com \
    --cc=rientjes@google.com \
    --cc=wuxu.wu@huawei.com \
    --cc=zhangyiru3@huawei.com \
    /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