public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
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 21:37:15 +0100	[thread overview]
Message-ID: <Zckv-93zIsXvmc3G@debian> (raw)
In-Reply-To: <47dmavi2ewo6pyxfoydqv5ztl35nuixe5z5wydqixozognii3v@tarta.nabijaczleweli.xyz>

[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]

Hi!,

On Sun, Feb 11, 2024 at 09:00:04PM +0100, наб wrote:
> Hi!
> 
> On Sun, Feb 11, 2024 at 07:56:39PM +0100, Alejandro Colomar wrote:
> > On Thu, Feb 08, 2024 at 09:43:21PM +0100, наб wrote:
> > > +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.
> This is what the official nomenclature seems to be:
>   https://wiki.debian.org/ppc64el says
>   > News
>   > 
>   > The IBM POWER platform, code name ppc64el, is an official architecture since
>   > DebianJessie.
>   > 
>   > Required Hardware
>   > 
>   > Debian/ppc64el requires, at minimum, a POWER8 processor machine. Although
>   > Debian was initially bootstrapped on a POWER7 set of servers, this class of
>   > server is not supported anymore, and you are not able to run Debian/ppc64el
>   > on a POWER 7 processor without hitting an illegal instruction fault.
>   > 
>   > There are, at this moment, a plenty of POWER8 machines being sold by
>   > different companies. 
> 
> All the branding I've ever seen in the modern world calls it POWER,
> and AIUI the PowerPC branding was abandoned like 15 years ago.
> 
> The debian wiki page even says
>   > The ppc64el port is not aimed for old Powerpc Macintosh machines,
>   > and, at the moment, there is no way to install it on this class of
>   > machines.
> but wikipedia tells me the last product from this line came out in 2006,
> which is pushing two decades by now. Even then, apparently
> "PowerPC is largely based on the earlier IBM POWER architecture"
> so it's the same thing.
> 
> Maybe when Apple had a choke-hold on the millennial mind a calling it
> "PowerPC" could've made sense, but through a modern lens PowerPC,
> to the extent it exists at all, is just a derivative of POWER I think
> 
> Best,

Hmmm, thanks!  Could you include this (or an excerpt if you prefer) in
the commit message, since we're changing the nomenclature?

Have a lovely night!
Alex

-- 
<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 --]

  reply	other threads:[~2024-02-11 20:37 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
2024-02-11 20:00   ` наб
2024-02-11 20:37     ` Alejandro Colomar [this message]
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=Zckv-93zIsXvmc3G@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