Re: autovectorize page checksum code included elsewhere - Mailing list pgsql-hackers

From John Naylor
Subject Re: autovectorize page checksum code included elsewhere
Date
Msg-id CANWCAZZ9Sb-cW4GWBhGGH7v-40s6gDK+15t1sVfS__VSCvhe8Q@mail.gmail.com
Whole thread Raw
In response to autovectorize page checksum code included elsewhere  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: autovectorize page checksum code included elsewhere
List pgsql-hackers
On Tue, Nov 7, 2023 at 9:47 AM Nathan Bossart <nathandbossart@gmail.com> wrote:
>
> Presently, we ask compilers to autovectorize checksum.c and numeric.c.  The
> page checksum code actually lives in checksum_impl.h, and checksum.c just
> includes it.  But checksum_impl.h is also used in pg_upgrade/file.c and
> pg_checksums.c, and since we don't ask compilers to autovectorize those
> files, the page checksum code may remain un-vectorized.

Poking in those files a bit, I also see references to building with
SSE 4.1. Maybe that's an avenue that we should pursue? (an indirect
function call is surely worth it for page-sized data)



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Lockless exit path for ReplicationOriginExitCleanup
Next
From: Cédric Villemain
Date:
Subject: Re: Extension Enhancement: Buffer Invalidation in pg_buffercache