From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: David Polakovic <email@dpolakovic.space>,
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>,
"H. Peter Anvin" <hpa@zytor.com>,
"Alexander Lobakin" <alexandr.lobakin@intel.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: proposition for fixing Y292B bug
Date: Mon, 1 Jul 2024 15:31:31 +0200 [thread overview]
Message-ID: <cef39a6f-426d-4c4d-950e-edbbe5e95acf@intel.com> (raw)
In-Reply-To: <ZoJx5GaBDHg7nayw@archie.me>
From: Bagas Sanjaya <bagasdotme@gmail.com>
Date: Mon, 1 Jul 2024 16:07:48 +0700
> On Sun, Jun 30, 2024 at 05:27:24PM +0200, David Polakovic wrote:
>> Thanks for reply.
>
> Please don't top-post on LKML, reply inline with appropriate context
> instead.
>
>>
>> My proposed solution was to create this BigInt datatype, which
>> stores the value in array. The functions for division, multiplication,
>> addition, subtraction and comparison could be stored in separate
>> ".h" library for manipulation with BigInt datatype. The paper speaks
>> more in detail.
IRRC there is big integer type somewhere in either lib/ or crypto/,
I don't remember exactly. It's used only for crypto tho.
>>
>> And yes, this truly is an userspace solution, but for kernel space
>> implementation I have zero to none experience. Therefore I wrote
>> here.
>
> There was a proposal for adding 128-bit unsigned integer (see [1]).
> The signed counterpart should be analogous.
I have generic 128-bit integer API/infra for the kernel in my internal
repo. I've been planning to upstream it for a couple years already, but
every time couldn't find a slot to do that.
I can upload it to my open GitHub, so that maybe someone else who needs
it could pick it up?
>
> Thanks.
>
> [1]: https://lore.kernel.org/lkml/20220722145514.767592-1-alexandr.lobakin@intel.com/
Thanks,
Olek
next prev parent reply other threads:[~2024-07-01 13:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 8:05 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 [this message]
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
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=cef39a6f-426d-4c4d-950e-edbbe5e95acf@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexandr.lobakin@intel.com \
--cc=bagasdotme@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®