Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 21 Apr 2023 08:34:47 +0200
From:   Willy Tarreau <w@1wt.eu>
To:     Bagas Sanjaya <bagasdotme@gmail.com>
Cc:     =?iso-8859-1?Q?Andr=E9?= Coelho <andrealbergaria@gmail.com>,
        linux-kernel@vger.kernel.org
Subject: Re: strings
Message-ID: <ZEIuh80SfDms30dc@1wt.eu>
References: <8de1912e-8009-3c85-ece5-7ca7f03be42a@gmail.com>
 <ZEIPKhKNz7LnhM/q@debian.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <ZEIPKhKNz7LnhM/q@debian.me>
Precedence: bulk

[dropped innocents from the CC list]

On Fri, Apr 21, 2023 at 11:20:58AM +0700, Bagas Sanjaya wrote:
> On Thu, Apr 20, 2023 at 03:58:47AM +0100, Andr? Coelho wrote:
> > greeting...if youre interessed in string algorihtm check
> > 
> > https://andrealbergaria.github.io/
> > 
> 
> Looks like above link is about hex arithmetic implemented using strings,
> right?

It looks more like a reinvention of the classical multi-byte string
processing (memcmp, memcpy, memmove etc).

> Also, on what use cases can your idea fit the kernel context? Or doesn't the
> kernel already have the implementation yet?

Sure it does, look at __crypto_memneq() for example, or more generally
at any memcmp() or memcpy() implementation from the last 30 years, for
example in glibc.

Regards,
Willy