all 6 comments

sorted by: hot top controversial new old
[–] 7 points 1 year ago (4 children)
  • Man, it’s so annoying to have to use multiple machines because one isn’t beefy enough!
  • We can now shove the hardware of 10 machines into one, making it the beefiest!
  • Man, it’s so annoying to have to use such a beefy machine!
  • We can now divide a beefy machine into 10 mediocre ones, just like you always wanted!

Make it make sense to me.

  • source
  • hideshow 4 child comments
  • [–] 13 points 1 year ago

    Not sure if you're being sarcastic or not, but the point of this is to reduce overhead associated with virtualization (aka VMs). Few workloads are able to take advantage of the massive compute resources that a single beefy machine has, so partitioning it is the most efficient use of resources, especially in data centers where maximizing efficiency is important.

  • source
  • parent
  • [–] 4 points 1 year ago

    I wish we'd get a proper microkernel, instead. If we're going to accept some performance degradation, let's get some benefit from it.

    Again: I have high hopes for Redox.

  • source
  • parent
  • [–] 1 point 1 year ago

    It seems like multikernel technologies's solution of kernel on dedicated cores but shareing hardware and kerbel IPC adds more novel use cases (like live kernel hand offs!) But this is probally better in isolation caps (closer to trad vms).

    man the scale of proc isolation from unikernal to kernel mods to ebpf to threads to children to forks to seperate procs to wasm to cgroups to containers to lxd to multi kenerl with ipc and now parker and finally full on virtualized hardware.

    All of that running in combinations on the same CPU. Itll be really cool to see what kind of abstractions we will make to make it easier to compose all that into patterns that are useful.

  • source
  • 25 comments in c/linux@lemmy.ml view that post
    [–] 16 points 1 year ago (1 child)

    They call it Parker because it's almost, but not quite, the right thing.

  • source
  • hideshow 1 child comment
  • [–] 13 points 1 year ago (1 child)

    Docker has little overhead and wouldn't this require running the entire kernelmultiple times, take up more RAM?

    Also dynamically allocating the RAM seems more efficient than having to assign each kernel a portion at boot.

  • source
  • hideshow 1 child comment
  • [–] 9 points 1 year ago

    If this works out, it's likely something that container engines would take advantage of as well. It may take more resources to do (we'll have to see), but adding kernel isolation would make for a much stronger sandbox. Containers are just a collection of other isolation tools like this anyway.

    gvisor already exists for environments like this, where the extra security at the cost of some performance is welcome. But having support for passing processes an isolated, hardened kernel from the primary running Linux kernel would probably make a lot of that performance gap disappear.

    I'm also thinking it could do wonders for compatibility too, since you could bundle abandoware apps with an older kernel, or ship new apps that require features from the latest kernel to places that wouldn't normally have those capabilities.

  • source
  • parent
  • [–] 11 points 1 year ago (5 children)

    I remember partitioned systems being a big thing in like the '90s '00s since those were the days you would pour $$$$ into large systems. But I thought the "cattle not pets" movement did away with that? Are we back to the days of "big iron"?

  • source
  • hideshow 5 child comments
  • [–] 4 points 1 year ago (2 children)

    What do you think all those cattle run on?

    Just big ass servers with tons of cores and ram.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago (1 child)

    I figured it was cattle all the way down. Even if they're big. Especially when you have thousands of them.

    Though maybe these setups can be scripted/automated to be easy to replicate and reproduce?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago

    Constant back and forth. Moving things closer increases efficenicy moving them apart increases resillency.

    So we are constantly shuffling between the two for different workloads to optimize for the given thing.

    That said i see this as an extension too the cattle idea by making even the kernel a thing to raised and culled on demand. This matter a lot more with heavy workloads like HPC and AI stuff where a process can be measure in days or weeks and stable uptime is paramount, vs the stateless work of intended k8s stuff (i say intended because you can k8s all the things now but it needs extensions to handle the new lifecycles).

  • source
  • parent
  • [–] 10 points 1 year ago* (1 child)

    If we're going to this amount of trouble, wouldn't it be better to replace the monolithic kernel with a microkernel and servers that provide the same APIs for Linux apps? Maybe even seL4 which has its behaviour formally verified. That way the microkernel can spin up arbitrary instances of whatever services are needed most.

  • source
  • hideshow 1 child comment
  • [–] 10 points 1 year ago (5 children)

    How is this better than a hypervisor OS running multiple VM's?

  • source
  • hideshow 5 child comments
  • [–] 13 points 1 year ago*

    I imagine there's some overhead savings but I don't know what. I guess with classic hypervisor there's still calls going through the host kerbel whereas with this they'd go straight to the hardware without special passthrough features?

  • source
  • parent
  • [–] 4 points 1 year ago

    Saving on some overhead, because the hypervisor is skipped. Things like disk IO to physical disks can be more efficient using multikernel (with direct access to HW) than VMs (which have to virtualize at least some components of HW access).

    With the proposed "Kernel Hand Over", it might be possible to send processes to another kernel entirely. This would allow booting a completely new kernel, moving your existing processes and resources over, then shutting down the old kernel, effectively updating with zero downtime.

    It will definitely take some time for any enterprises to transition over (if they have a use for this), and consumers will likely not see much use in this technology.

  • source
  • parent
  • [–] 4 points 1 year ago

    I recently heard this great phrase:

    "A VM makes an OS believe that it has the machine to itself; a container makes a process believe that it has the OS to itself."

    This would be somewhere between that, where each container could believe it has the OS to itself, but with different kernels.

  • source
  • parent
  • [–] 1 point 1 year ago (1 child)

    I mean isn't this just Xen revisited? I don't understand why this is necessary.

  • source
  • hideshow 1 child comment
  • [–] 5 points 1 year ago* (last edited 1 year ago)

    Xen is running full virtual machines. You run full operating systems on simulated hardware. The real “host” operating system is the hypervisor (Xen). Inside a VM, you have the concept of one or more CPUs but you do not know which actual CPU cores that maps to. The load can be distributed to any of them by the real host.

    In something like Docker, you only run a single host kernel. On top of that you run sandbox environments that run on the kernel that “think” they have an environment to themselves but are actually sharing a single host kernel. The single host kernel directly manages the real hardware. Processes can run on any of the CPUs managed by the single host kernel.

    In both of the above, updating the host means shutting the system down.

    With this new approach, you have multiple kernels, all running natively on real hardware. Any given CPU is being managed by only one of the kernels. No hypervisor.

  • source
  • parent
  • [+] -9 points 1 year ago (4 children)

    GTFO, you're the brainrot ai slop hosting TikTok company.

  • source
  • hideshow 4 child comments
  • [–] 9 points 1 year ago (2 children)

    Code is code. If it's good Free code, I'll use it. I also don't like Microsoft and Facebook but I run their kernel code too.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 1 year ago (1 child)

    Why should i trust them with this multi-kernel thingy if they let the dumpster fire that is tiktok, exist? And, they're probably trying to embrace-extend-extinguish Linux just like microsoft and apple with their WSL and Containers.app respectively.

  • source
  • parent
  • hideshow 1 child comment