Announcement

Collapse
No announcement yet.

Alpine Linux 3.15 Released - Builds Off Linux 5.15, Drops MIPS64, SimpleDRM For FB

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
    aht0
    Senior Member

  • aht0
    replied
    Originally posted by Naib View Post
    Should do. I run alpine on bare metal and also in dozens of containers
    Had distinct issue with using Nvidia card on Alpine. Because musl and Nvidia driver didn't mix well. So I am curious whether AMDGPU would be also depending on the existence of glibc.

    Leave a comment:

  • ncopa
    Phoronix Member

  • ncopa
    replied
    Originally posted by timofonic View Post

    What about adding Zstd support to busybox?

    It seems somebody tried it in September 2021, this year.
    As said, we are not there yet. I think it needs to first be added to busybox, and only after that we can use zstd for kernel modules. And there are no guarantees that a busybox implementation will have the performance benefits, as they focus primarily on size.

    Feel free to work on getting it into busybox.

    Leave a comment:

  • timofonic
    Senior Member

  • timofonic
    replied
    Originally posted by ncopa View Post

    Because it does not work with busybox modprobe. We actually used zstd first, and added the extra 1MB for kmod (same size as entire busybox btw...). But then it was discovered that there are also some kubernetes tools like `kube-router` that uses busybox modprobe. We ran some tests to compare with gz and the difference was not that big so it was simply not worth the downsides.

    See https://gitlab.alpinelinux.org/alpin...-/issues/12857 for the details
    What about adding Zstd support to busybox?

    It seems somebody tried it in September 2021, this year.

    http://lists.busybox.net/pipermail/b...er/089179.html
    timofonic
    Senior Member
    Last edited by timofonic; 26 November 2021, 11:52 AM.

    Leave a comment:

  • Naib
    Senior Member

  • Naib
    replied
    Should do. I run alpine on bare metal and also in dozens of containers

    Leave a comment:

  • aht0
    Senior Member

  • aht0
    replied
    Would it run on bare metal in combination with Vega dGPU?

    Leave a comment:

  • sinepgib
    Senior Member

  • sinepgib
    replied
    Originally posted by tildearrow View Post

    With older kernels. As an example, my Arch system broke when I upgraded and mkinitcpio was set to generate Zstd-compressed initrd, so that prevented me from booting since my kernel (5.4) did not have Zstd baked in.
    But that's my point. You can't have that scenario with modules because, unless they're made for the same kernel version, they are quite unlikely to work at all anyway. And if you know the kernel you build your modules against you know for certain whether it supports zstd or not. The mkinitcpio is a completely different scenario because initramfs is an interface with userspace and it's expected to be arbitrary as long as the file format matches and it provides some kind of init.

    Leave a comment:

  • ncopa
    Phoronix Member

  • ncopa
    replied
    Originally posted by sdack View Post
    Why use Gzip to compress kernel modules? Seems like an odd choice.
    Because it does not work with busybox modprobe. We actually used zstd first, and added the extra 1MB for kmod (same size as entire busybox btw...). But then it was discovered that there are also some kubernetes tools like `kube-router` that uses busybox modprobe. We ran some tests to compare with gz and the difference was not that big so it was simply not worth the downsides.

    See https://gitlab.alpinelinux.org/alpin...-/issues/12857 for the details

    Leave a comment:

  • tildearrow
    Senior Member

  • tildearrow
    replied
    Originally posted by sinepgib View Post

    Compatibility with what? Kernel and modules are tightly coupled. Either you have a version that supports it and all your modules can use it or you don't. There's no chance of mismatch there that can result on a properly running system.
    With older kernels. As an example, my Arch system broke when I upgraded and mkinitcpio was set to generate Zstd-compressed initrd, so that prevented me from booting since my kernel (5.4) did not have Zstd baked in.

    Leave a comment:

  • sinepgib
    Senior Member

  • sinepgib
    replied
    Originally posted by tildearrow View Post

    Maybe compatibility? Zstd in kernel is a fairly new feature...
    Compatibility with what? Kernel and modules are tightly coupled. Either you have a version that supports it and all your modules can use it or you don't. There's no chance of mismatch there that can result on a properly running system.

    Leave a comment:

  • discordian
    Senior Member

  • discordian
    replied
    Originally posted by caligula View Post

    How is it related? The .ko files are compressed by the kernel make scripts.
    The kmod/insmod/modprobe tools decompress the module. The kernel never does.

    Doesnt seem to be much progress, but a patch for bb is available:
    http://lists.busybox.net/pipermail/b...er/089179.html

    Leave a comment:

Working...
X