From: Alejandro Colomar <alx@kernel.org>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] pthread_create.3: re-do the architecture/default stack size mapping
Date: Sun, 11 Feb 2024 19:56:39 +0100 [thread overview]
Message-ID: <ZckYZ2q0PQIWFqrq@debian> (raw)
In-Reply-To: <4wwe76cvuczjn57bzw7wd4derfaufcgrxr5skvlu25wvwecmmh@tarta.nabijaczleweli.xyz>
[-- Attachment #1: Type: text/plain, Size: 3122 bytes --]
Hi наб,
On Thu, Feb 08, 2024 at 09:43:21PM +0100, наб wrote:
> Currently, the page lists 2 of the 3 x86 architectures, no ARM(!),
> old PowerPC only, and most egregiously itanium,
> which linux doesn't target.
>
> Per glibc 2.38:
> $ git grep ARCH_STACK_DEFAULT_SIZE
> aarch64 #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> arc #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> arm #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> csky #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> loongarch #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> m68k #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> microblaze #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> mips #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> nios2 #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> or1k #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> riscv #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> s390 #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> sh #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> sparc32 #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
> x86 #define ARCH_STACK_DEFAULT_SIZE (2 * 1024 * 1024)
>
> alpha #define ARCH_STACK_DEFAULT_SIZE (4 * 1024 * 1024)
> powerpc #define ARCH_STACK_DEFAULT_SIZE (4 * 1024 * 1024)
> sparc64 #define ARCH_STACK_DEFAULT_SIZE (4 * 1024 * 1024)
>
> hppa #define ARCH_STACK_DEFAULT_SIZE (8 * 1024 * 1024)
>
> ia64 #define ARCH_STACK_DEFAULT_SIZE (32 * 1024 * 1024)
>
> I cut PA-RISC and the Alpha. They have 10 and 6 popcon entries,
> respectively, and AFAICT they haven't seen a processor released
> in over a decade ‒ they aren't relevant to any modern reader.
>
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> ---
> man3/pthread_create.3 | 19 ++-----------------
> 1 file changed, 2 insertions(+), 17 deletions(-)
>
> diff --git a/man3/pthread_create.3 b/man3/pthread_create.3
> index 66c67a6ff..fd6253bf4 100644
> --- a/man3/pthread_create.3
> +++ b/man3/pthread_create.3
> @@ -200,23 +200,8 @@ .SH NOTES
> If the
> .B RLIMIT_STACK
> resource limit is set to "unlimited",
> -a per-architecture value is used for the stack size.
> -Here is the value for a few architectures:
> -.RS
> -.TS
> -allbox;
> -lb lb
> -l r.
> -Architecture Default stack size
> -i386 2 MB
> -IA-64 32 MB
> -PowerPC 4 MB
> -S/390 2 MB
> -Sparc-32 2 MB
> -Sparc-64 4 MB
> -x86_64 2 MB
> -.TE
> -.RE
> +a per-architecture value is used for the stack size:
> +2 MB on most architectures; 4 MB on POWER and Sparc-64.
Why capitalize POWER and omit PC? Other than that, LGTM.
Thanks for the patch.
Have a lovely day!
Alex
> .SH BUGS
> In the obsolete LinuxThreads implementation,
> each of the threads in a process has a different process ID.
> --
> 2.39.2
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-11 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 20:43 [PATCH] pthread_create.3: re-do the architecture/default stack size mapping наб
2024-02-11 18:56 ` Alejandro Colomar [this message]
2024-02-11 20:00 ` наб
2024-02-11 20:37 ` Alejandro Colomar
2024-02-11 22:27 ` [PATCH v2] " наб
2024-02-11 23:50 ` Alejandro Colomar
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=ZckYZ2q0PQIWFqrq@debian \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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