News for hackers. Stuff that matters.
Re:Oxide Computer Company: Initial boot sequence by jonny_eh on Monday December 02, 2019 @12:25PM (#21684492)
> custom cloud hardware

Uhh, you mean computers?

Re:Oxide Computer Company: Initial boot sequence by sangnoir on Monday December 02, 2019 @12:33PM (#21684568)
Looking at their pedigree, I'd hazard that the computers are geared towards running containerized workloads, so "custom cloud hardware" sounds about right.
Re:Oxide Computer Company: Initial boot sequence by codeflo on Monday December 02, 2019 @12:47PM (#21684741)
That seems to be the common theory, but what does that even mean? There's nothing all that special about running containers at the hardware level, they are really just groups of processes that the kernel manages a certain way.
Re:Oxide Computer Company: Initial boot sequence by mochomocha on Monday December 02, 2019 @01:21PM (#21685130)
That's not completely accurate. Hardware & OSes have not been designed for heavy multi-tenancy, leading to (among other issues) cache interference. At Netflix [1], we have to do quite a bit of work to undo that. Bigger orgs like Google have spent more than a decade improving the Linux scheduler in their own fork for similar reasons.

[1] https://medium.com/netflix-techblog/predictive-cpu-isolation...

Re:Oxide Computer Company: Initial boot sequence by codeflo on Monday December 02, 2019 @02:33PM (#21685947)
Very interesting link, thanks. Obviously your use case goes way beyond running a standard Docker installation. It sounds like you really want the kernel to schedule containers instead of processes -- which it doesn't really do by default, hence my comment. Perhaps it shouldn't be surprising, that you're able to get these clear performance gains from a highly optimized special-purpose scheduler. Still, I was a bit surprised. :)

However, that's at the OS level. What can realistically be done at the hardware level? It must be possible in theory to design a CPU that's better at this kind of context switching, but I don't know if a new "computer company" really wants to go there.

Re:Oxide Computer Company: Initial boot sequence by shaklee3 on Tuesday December 03, 2019 @01:04AM (#21690318)
While that's true, this particular company doesn't seem to be targeting anything that would improve containers (OS optimizations, new CPU). So I think the OP was correct in that simply changing the BMC or making it more secure on boot won't affect containers.
Re:Oxide Computer Company: Initial boot sequence by puzza007 on Tuesday December 03, 2019 @04:04AM (#21690951)
I'd be surprised if they didn't leverage something like the SmartOS container capabilities https://www.joyent.com/smartos
Re:Oxide Computer Company: Initial boot sequence by hector_vasquez on Monday December 02, 2019 @01:38PM (#21685330)
People who worked at Docker, Joyent, and Sun would be the ones to answer your question :). Consider the possibility that the kernel and the h/w are increasingly at odds on commodity server hardware.
[dead]
Re:Oxide Computer Company: Initial boot sequence by LegitShady on Monday December 02, 2019 @01:18PM (#21685097)
He means technically practically what is the difference?
Re:Oxide Computer Company: Initial boot sequence by darkarmani on Monday December 02, 2019 @02:37PM (#21685986)
My watch is a computer, so I don't think they want to make general purpose computers.