Re: Popcount optimization using AVX512

Nathan Bossart <nathandbossart@gmail.com>

From: Nathan Bossart <nathandbossart@gmail.com>

To: "Amonson, Paul D" <paul.d.amonson@intel.com>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, David Rowley <dgrowleyml@gmail.com>, Andres Freund <andres@anarazel.de>, Alvaro Herrera <alvherre@alvh.no-ip.org>, "Shankaran, Akash" <akash.shankaran@intel.com>, Noah Misch <noah@leadboat.com>, Matthias van de Meent <boekewurm+postgres@gmail.com>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>

Date: 2024-03-29T20:57:41Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix __attribute__((target(...))) usage.
- 41b98ddb77bf 18.0 landed
Use __attribute__((target(...))) for AVX-512 support.
- f78667bd910e 18.0 landed
Fix code for probing availability of AVX-512.
- 598e0114a3b1 17.0 landed
Optimize visibilitymap_count() with AVX-512 instructions.
- 41c51f0c68b2 17.0 landed
Optimize pg_popcount() with AVX-512 instructions.
- 792752af4eb5 17.0 landed
Inline pg_popcount() for small buffers.
- deb1486c7d36 17.0 landed
Avoid function call overhead of pg_popcount() in syslogger.c.
- 4133c1f45c54 17.0 landed
Refactor code for setting pg_popcount* function pointers.
- 6687430c98f3 17.0 landed
Inline pg_popcount{32,64} into pg_popcount().
- cc4826dd5e52 17.0 landed
Remove MSVC scripts
- 1301c80b2167 17.0 cited
Use ARMv8 CRC instructions where available.
- f044d71e331d 11.0 cited
Use Intel SSE 4.2 CRC instructions where available.
- 3dc2d62d0486 9.5.0 cited

On Fri, Mar 29, 2024 at 03:08:28PM -0500, Nathan Bossart wrote:
>> +#if defined(HAVE__GET_CPUID)
>> +	__get_cpuid_count(7, 0, &exx[0], &exx[1], &exx[2], &exx[3]);
>> +#elif defined(HAVE__CPUID)
>> +	__cpuidex(exx, 7, 0);
> 
> Is there any reason we can't use __get_cpuid() and __cpuid() here, given
> the sub-leaf is 0?

The answer to this seems to be "no."  After additional research,
__get_cpuid_count/__cpuidex seem new enough that we probably want configure
checks for them, so I'll add those back in the next version of the patch.

Apologies for the stream of consciousness today...

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com