From: Mike Kravetz <mike.kravetz@oracle.com>
To: zhangyiru <zhangyiru3@huawei.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, mhocko@suse.com, wuxu.wu@huawei.com,
liusirui@huawei.com, liuzixian4@huawei.com
Subject: Re: [PATCH v4] mm,hugetlb: remove mlock ulimit for SHM_HUGETLB
Date: Mon, 11 Oct 2021 14:39:53 -0700 [thread overview]
Message-ID: <fa3dde27-fec4-5374-79d0-f9db77a60840@oracle.com> (raw)
In-Reply-To: <20211009094355.127705-1-zhangyiru3@huawei.com>
On 10/9/21 2:43 AM, zhangyiru wrote:
> commit 21a3c273f88c9cbbaf7e ("mm, hugetlb: add thread name and pid to
> SHM_HUGETLB mlock rlimit warning") marked this as deprecated in 2012,
> but it is not deleted yet.
>
> Mike says he still see that message in log files on occasion,
> so maybe we should preserve this warning.
>
> Signed-off-by: zhangyiru <zhangyiru3@huawei.com>
Thanks,
Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
It will be interesting to see if anyone notices the change in behavior.
My 'guess' is that it will not be noticed until this is picked up by
distros, which may take quite some time.
--
Mike Kravetz
next prev parent reply other threads:[~2021-10-11 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 9:43 [PATCH v4] mm,hugetlb: remove mlock ulimit for SHM_HUGETLB zhangyiru
2021-10-11 21:39 ` Mike Kravetz [this message]
2021-11-01 7:01 ` Hugh Dickins
2021-11-01 19:44 ` [PATCH v5] " zhangyiru
2021-11-01 21:09 ` [PATCH v6] " zhangyiru
2021-11-01 23:05 ` Mike Kravetz
2021-11-02 15:40 ` [PATCH v7] " zhangyiru
2021-11-02 19:46 ` Mike Kravetz
2021-11-03 10:58 ` [PATCH v8] " zhangyiru
2021-11-03 17:19 ` Mike Kravetz
2021-11-01 21:39 ` [PATCH v4] " Mike Kravetz
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=fa3dde27-fec4-5374-79d0-f9db77a60840@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=liusirui@huawei.com \
--cc=liuzixian4@huawei.com \
--cc=mhocko@suse.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;
as well as URLs for NNTP newsgroup(s).