| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | John Naylor <johncnaylorls(at)gmail(dot)com>, "Chiranmoy(dot)Bhattacharya(at)fujitsu(dot)com" <Chiranmoy(dot)Bhattacharya(at)fujitsu(dot)com>, "Devanga(dot)Susmitha(at)fujitsu(dot)com" <Devanga(dot)Susmitha(at)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "Ragesh(dot)Hajela(at)fujitsu(dot)com" <Ragesh(dot)Hajela(at)fujitsu(dot)com> |
| Subject: | Re: [PATCH] Hex-coding optimizations using SVE on ARM. |
| Date: | 2025-01-14 16:57:51 |
| Message-ID: | Z4aXj_fJYCQ6GBbC@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 14, 2025 at 12:59:04AM -0500, Tom Lane wrote:
> John Naylor <johncnaylorls(at)gmail(dot)com> writes:
>> We can do about as well simply by changing the nibble lookup to a byte
>> lookup, which works on every compiler and architecture:
Nice. I tried enabling auto-vectorization and loop unrolling on top of
this patch, and the numbers looked the same. I think we'd need CPU
intrinsics or an even bigger lookup table to do any better.
> I didn't attempt to verify your patch, but I do prefer addressing
> this issue in a machine-independent fashion. I also like the brevity
> of the patch (though it could do with some comments perhaps, not that
> the existing code has any).
+1
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2025-01-14 17:08:36 | Re: New GUC autovacuum_max_threshold ? |
| Previous Message | Yugo NAGATA | 2025-01-14 16:40:46 | Re: Allow ILIKE forward matching to use btree index |