From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
David Polakovic <email@dpolakovic.space>,
Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Lobakin <alexandr.lobakin@intel.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: proposition for fixing Y292B bug
Date: Fri, 5 Jul 2024 21:17:10 +0700 [thread overview]
Message-ID: <ZogAZltQIks_cN-y@archie.me> (raw)
In-Reply-To: <848ADF85-6138-4D56-8DDD-E327B8AFC5EC@zytor.com>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
On Thu, Jul 04, 2024 at 07:59:13PM -0700, H. Peter Anvin wrote:
> On July 3, 2024 8:29:58 AM PDT, David Polakovic <email@dpolakovic.space> wrote:
> >I am not sure if I don't understand your solution, but extending the
> >memory designation from 64 to 128 bits, is another temporary
> >solution, which will again overflow one day.
> >
> >The sole reason why I was proposing the new "BigInt" type was to
> >store each digit of the time_c as separate element of array, which
> >could be resized (added one digit) as needed. The only limit would
> >then be the physical amount of memory in the machine.
> >
> >dpo
> >
>
> So now you are worried about the Y5e30 problem?!
>
> You realize that you are now talking the orders of magnitude of time for which:
>
> " The estimated time until most or all of the remaining 1–10% of stellar remnants not ejected from galaxies fall into their galaxies' central supermassive black holes. By this point, with binary stars having fallen into each other, and planets into their stars, via emission of gravitational radiation, only solitary objects (stellar remnants, brown dwarfs, ejected planetary-mass objects, black holes) will remain in the universe."
>
> I genuinely thought this whole thread was a practical joke...
And that's what I thought as unnecessary engineering churn...
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-07-05 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 8:05 proposition for fixing Y292B bug David Polakovic
2024-06-30 13:41 ` Bagas Sanjaya
2024-06-30 15:27 ` David Polakovic
2024-07-01 9:07 ` Bagas Sanjaya
2024-07-01 13:31 ` Alexander Lobakin
2024-07-03 15:29 ` David Polakovic
2024-07-04 17:49 ` Theodore Ts'o
2024-07-04 21:13 ` David Polakovic
2024-07-05 14:12 ` Bagas Sanjaya
2024-07-05 2:59 ` H. Peter Anvin
2024-07-05 14:17 ` Bagas Sanjaya [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=ZogAZltQIks_cN-y@archie.me \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aleksander.lobakin@intel.com \
--cc=alexandr.lobakin@intel.com \
--cc=email@dpolakovic.space \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
/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.