Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

[flagged]


The article discusses this in the conclusion:

> We are going to submit this work for inclusion in the main kernel source tree, but most likely not in its current form. Although the results look encouraging we have to remember that Linux is a highly portable operating system: it runs on powerful servers as well as small resource constrained IoT devices and on many other CPU architectures as well. The current version of the patches just optimises disk encryption for a particular workload on a particular architecture, but Linux needs a solution which runs smoothly everywhere.

That is, they think their current patch is too specialized for their own use-case to warrant inclusion in the mainline kernel without significant adaptation.


>but there doesn't appear to have been any serious effort to coordinate with other Linux contributors to figure out a solution to the problem.

Well when they reached out to the community they were told they're idiots and should f* off in only somewhat nicer language. Then they were simply ignored.

When your community is toxic don't complain that people don't want to be part of it.


They are submitting their work, after they put in even more work to make it more universally applicable to all Linux users. They also did try to engage with the community who basically told them that they didn't know how fast crypto should be.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: