this post was submitted on 11 Jan 2025
22 points (100.0% liked)

Programming

17788 readers
98 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

Neat article about avoiding a memcpy in a circular buffer.

you are viewing a single comment's thread
view the rest of the comments
[–] palordrolap@fedia.io 1 points 1 day ago

I feel like there could be a decent intermediate option here. It quickly glosses over page sizes and then talks about the modulus operator, but misses the fact that bitwise operations can emulate modulus for powers of two, which is generally the sorts of sizes that pages tend to be, and bitwise is generally much faster than the division that modulus performs.

In short, x % z is generally equivalent to x & (z-1) when z is a power of two and is often much faster.

Now, I get that the compiler might be clever enough to turn a modulus operation of the right size into a bitwise operation, but it's still necessary that the programmer specify that power-of-two size for their circular buffer in the first place.

I would be curious as to whether this "greyer" magic has any benefit when not performing the page table hack.