From: "Yang Xu (Fujitsu)" <xuyang2018.jy@fujitsu.com>
To: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2 1/2] swapon.2: Adjust decreased value under CONFIG_MIGRATION
Date: Fri, 15 Dec 2023 07:49:22 +0000 [thread overview]
Message-ID: <e957c61a-93b3-478c-aede-eec2b09105cf@fujitsu.com> (raw)
In-Reply-To: <03fc8738-f3b3-4caa-ab76-49883814ac3c@fujitsu.com>
Hi all,
Sorry, I forgot to send this "ping mail" to man-pages.
PING
Best Regards
Yang Xu
> Hi all,
>
> Ping
>
> Best Regards
> Yang Xu
>
>> After kernel 5.19[1], the limit is decreased by 3.
>>
>> [1]https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/linux/swap.h?id=6c287605f
>>
>> Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>
>> ---
>> man2/swapon.2 | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/man2/swapon.2 b/man2/swapon.2
>> index c0e61cbc6..2bc477d18 100644
>> --- a/man2/swapon.2
>> +++ b/man2/swapon.2
>> @@ -164,7 +164,8 @@ Before Linux 2.4.10,
>> .B MAX_SWAPFILES
>> has the value 8;
>> since Linux 2.4.10, it has the value 32.
>> -Since Linux 2.6.18, the limit is decreased by 2 (thus: 30)
>> +Since Linux 2.6.18, the limit is decreased by 2 (Since Linux 5.19.0,
>> +the limit is decreased by 3)
>> if the kernel is built with the
>> .B CONFIG_MIGRATION
>> option
>
next prev parent reply other threads:[~2023-12-15 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 6:30 [PATCH v2 1/2] swapon.2: Adjust decreased value under CONFIG_MIGRATION Yang Xu
2023-12-05 6:30 ` [PATCH v2 2/2] swapon.2: Adjust decreased value under CONFIG_PTE_MARKER Yang Xu
2023-12-15 11:11 ` Alejandro Colomar
[not found] ` <03fc8738-f3b3-4caa-ab76-49883814ac3c@fujitsu.com>
2023-12-15 7:49 ` Yang Xu (Fujitsu) [this message]
2023-12-15 11:13 ` [PATCH v2 1/2] swapon.2: Adjust decreased value under CONFIG_MIGRATION Alejandro Colomar
2023-12-15 11:27 ` Alejandro Colomar
2023-12-19 2:14 ` Yang Xu (Fujitsu)
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=e957c61a-93b3-478c-aede-eec2b09105cf@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--cc=linux-man@vger.kernel.org \
--cc=ltp@lists.linux.it \
/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