From: Chaitanya S Prakash <chaitanyas.prakash@arm.com>
To: David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 3/3] selftests: Set overcommit_policy as OVERCOMMIT_ALWAYS
Date: Mon, 20 Mar 2023 12:17:59 +0530 [thread overview]
Message-ID: <b68705c8-df85-6b45-091b-3975a89b796e@arm.com> (raw)
In-Reply-To: <8fe0d91b-2209-1c66-2788-f18055c9d213@redhat.com>
On 3/16/23 21:01, David Hildenbrand wrote:
> On 14.03.23 05:23, Chaitanya S Prakash wrote:
>> The kernel's default behaviour is to obstruct the allocation of high
>> virtual address as it handles memory overcommit in a heuristic manner.
>> Setting the parameter as OVERCOMMIT_ALWAYS, ensures kernel isn't
>> susceptible to the availability of a platform's physical memory when
>> denying a memory allocation request.
>
> Which tests in particular require that?
This is applicable to the virtual address range selftest.
>
> Subjects should start with "selftests/mm" instead of more generic
> "selftests:"
I'll make the necessary changes.
>
prev parent reply other threads:[~2023-03-20 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 4:23 [PATCH 0/3] selftests: Fix virtual address range for arm64 Chaitanya S Prakash
2023-03-14 4:23 ` [PATCH 1/3] selftests: Change MAP_CHUNK_SIZE Chaitanya S Prakash
2023-03-14 4:23 ` [PATCH 2/3] selftests: Change NR_CHUNKS_HIGH for aarch64 Chaitanya S Prakash
2023-03-14 4:23 ` [PATCH 3/3] selftests: Set overcommit_policy as OVERCOMMIT_ALWAYS Chaitanya S Prakash
2023-03-16 15:31 ` David Hildenbrand
2023-03-20 6:47 ` Chaitanya S Prakash [this message]
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=b68705c8-df85-6b45-091b-3975a89b796e@arm.com \
--to=chaitanyas.prakash@arm.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.