From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] [NOOB ALERT] Use amd64 kernel?
Date: Sat, 5 Feb 2022 15:12:59 -0800 [thread overview]
Message-ID: <Yf8Ee3QJcUdAdryV@wopr> (raw)
In-Reply-To: <C3896C04-4902-433D-AE3D-A6E848D18E86@web.de>
On Sat, Feb 05, 2022 at 10:11:47PM +0100, Alexander Shendi wrote:
> Hi,
>
> Thanks, but I know I can use the 9pc64 kernel. My reasoning was along these lines:
> 386: 32bit ints + pointers
> amd64: 64bit ints + pointers, potentially a waste for 2G RAM, but more CPU registers in amd64 long mode?
>
In your normal 9front usage, are you dangerously close to OOM
conditions? Is your software so meticulously optimized as to care how
many CPU registers are available? Flip a coin.
khm
prev parent reply other threads:[~2022-02-06 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 19:48 Alexander Shendi
2022-02-04 20:50 ` Amavect
2022-02-04 21:03 ` ori
2022-02-04 21:28 ` Mehmet Erol Sanliturk
2022-02-04 22:52 ` Alexander Shendi
2022-02-04 21:16 ` sirjofri
2022-02-05 17:41 ` Stanley Lieber
2022-02-05 21:11 ` Alexander Shendi
2022-02-05 23:12 ` Kurt H Maier [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=Yf8Ee3QJcUdAdryV@wopr \
--to=khm@sciops.net \
--cc=9front@9front.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 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).