What it takes to keep an enterprise 'Frankenkernel' alive (Register)
source link: https://lwn.net/Articles/936976/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
What it takes to keep an enterprise 'Frankenkernel' alive (Register)
So, what the team are working on is a Frankenstein's monster, sewn together from different codebases. Although the base kernel is still version 5.14, it is full of backports from upstream. It has the XFS filesystem code from kernel 6.0, the USB subsystem – complete with drivers – and BPF subsystem from kernel 6.2, the wireless stack and all drivers from kernel 6.3, and the multipath TCP/IP code from kernel 6.4 – which at the time of the talk hadn't even been released upstream yet.
(Log in to post comments)
What it takes to keep an enterprise 'Frankenkernel' alive (Register)
Posted Jun 30, 2023 15:07 UTC (Fri) by marcH (subscriber, #57642) [Link]
Similar to https://chromium.googlesource.com/chromiumos/docs/+/refs/... and likely others.
The common parts should be somewhat standardized at the git level. The ability to add a "JSON note" or something to each commit could be a good start?
What it takes to keep an enterprise 'Frankenkernel' alive (Register)
Posted Jun 30, 2023 15:49 UTC (Fri) by eharris (guest, #144549) [Link]
What it takes to keep an enterprise 'Frankenkernel' alive (Register)
Posted Jun 30, 2023 16:47 UTC (Fri) by pbonzini (subscriber, #60935) [Link]
What it takes to keep an enterprise 'Frankenkernel' alive (Register)
Posted Jun 30, 2023 16:53 UTC (Fri) by hkario (subscriber, #94864) [Link]
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK