Thread: Improve conditional compilation for direct I/O alignment checks

Improve conditional compilation for direct I/O alignment checks

From
Junwang Zhao
Date:
This patch refactors the alignment checks for direct I/O to preprocess phase,
thereby reducing some CPU cycles.

-- 
Regards
Junwang Zhao

Attachment
On Sun, May 26, 2024 at 3:16 PM Junwang Zhao <zhjwpku@gmail.com> wrote:
>
> This patch refactors the alignment checks for direct I/O to preprocess phase,
> thereby reducing some CPU cycles.
>
> --
> Regards
> Junwang Zhao

Patch v2 with some additional minor polishment of the comments in `mdwriteback`.

--
Regards
Junwang Zhao

Attachment

Re: Improve conditional compilation for direct I/O alignment checks

From
Peter Eisentraut
Date:
On 26.05.24 09:16, Junwang Zhao wrote:
> This patch refactors the alignment checks for direct I/O to preprocess phase,
> thereby reducing some CPU cycles.

This patch replaces for example

     if (PG_O_DIRECT != 0 && PG_IO_ALIGN_SIZE <= BLCKSZ)
         Assert((uintptr_t) buffer == TYPEALIGN(PG_IO_ALIGN_SIZE, buffer));

with

     #if PG_O_DIRECT != 0 && PG_IO_ALIGN_SIZE <= BLCKSZ
         Assert((uintptr_t) buffer == TYPEALIGN(PG_IO_ALIGN_SIZE, buffer));
     #endif

You appear to be assuming that this saves some CPU cycles.  But this is 
not the case.  The compiler will remove the unused code in the first 
case because all the constants in the if expression are known at 
compile-time.