News for hackers. Stuff that matters.
Re:Shift-to-Middle Array: A Faster Alternative to Std:Deque? by eru on Sunday March 23, 2025 @10:55PM (#43457492)
> In practice, the main problem is that you can't use private mappings (which are the default and for good reason); you have to use shared mapping, which are very finicky to set up and cause infelicities with `fork`. [This does make me wonder how reflinks/`copy_file_range` interact with `mmap` and the page cache.]

Yet another reason fork was never a good design choice.

Re:Shift-to-Middle Array: A Faster Alternative to Std:Deque? by fc417fc802 on Monday March 24, 2025 @04:53AM (#43458740)
Is fork really the problem in this scenario?
Re:Shift-to-Middle Array: A Faster Alternative to Std:Deque? by eru on Monday March 24, 2025 @11:43PM (#43467934)
I don't think it's the main problem here, but it's just another point where the fork/exec model shows its problems.
Re:Shift-to-Middle Array: A Faster Alternative to Std:Deque? by fc417fc802 on Tuesday March 25, 2025 @10:30AM (#43471799)
What would you replace fork with? I don't get it.

Isn't the desired improvement here to how the kernel handles the lifetime of mappings? It seems orthogonal to me.