Leveraging Zig's Allocators

Re:Leveraging Zig's Allocators by josephg on Saturday June 15, 2024 @05:45PM (#40692925)

For 8kb? Syscalling in to the kernel, updating the processes’s memory map and then later faulting is probably slower by an order of magnitude or more compared to just setting those bytes to zero.

Memcpy, bzero and friends are insanely fast. Practically free when those bytes are in the cpu’s cache already.

[ Parent | on HN ]

Re:Leveraging Zig's Allocators by astrange on Saturday June 15, 2024 @06:34PM (#40693205)

So don't syscall. Darwin has a system similar to io_uring for this.

(But it also has a 16KB page size.)

[ Parent | on HN ]

Re:Leveraging Zig's Allocators by josephg on Sunday June 16, 2024 @02:52AM (#40695172)

Probably still cause a page fault when the memory is re-accessed though. I suspect even using io_uring will still be a lot slower than bzero if you're just zeroing out 2 pages of memory. Zeroing memory is really fast.

[ Parent | on HN ]