NixOS Takes Action After 1.2GB/s ZFS Encryption Speed Drops To 200MB/s With Linux 5.0+

[birdie]

Virtualbox is far inferior to KVM/QEMU. What the fuck are you talking about.

And in many ways far superior.

[starshipeleven]

No real gamer/audio producer uses pulseaudio,

wrong for gamers, irrelevant for audio producers (as it's not designed for that anyway, they will want to use Jack as that's the right tool for the job)

networkmanager is buggy( see bug reports) and badly designed, it uses notifications from the driver level and user has no direct control,

Everything has bug reports, I have no idea of what you are talking about for the rest, and you probably don't either.

systemd does not run with the 3.14 android kernel because of the unimplemented syscall 279

new software does not run with old unsupported kernel modified to run a crap firmware for crap device. NOTABUG FIXYOUROWNSHIT

polkit is useless for desktop computers and causes extra work, see freedesktop.

you know what a "polkit" even is?

No windows users use gnome3, it is so bad, see what happened to win8.

what have windows users to do with anything.

[dnebdal]

Let's freeze this hate train a second and point out that the application does not need to ask the kernel to use AES-NI or any other CPU instruction directly, which is what it should have been doing all along.

(OpenSSH for example does it, so does OpenVPN)

Nope, they can't. When you do something with the FPU or SSE registers in the kernel, you need to save their previous state, and then restore them back to their old contents when you're done. The kernel saves/restores the common registers for you, but the math ones are more rarely used, so it saves time overall to not automatically do this on every interrupt and syscall. The functions that were removed and replaced with GPL-only ones are exactly these save/restore ones.

The reason OpenSSH and OpenVPN can do whatever they want is that they do it in userland, not in the kernel. Whenever there is a kernel/userland transition (syscalls, interrupts, the scheduler thinks it's time to switch task), the kernel does save/restore these registers. ZFS is a file system, so unlike vpn and ssh it has to work without any userland service running.

[aht0]

Would all this bsd lovers really like to have a fully integrated zfs in Linux? Then bsd would loose the only feature anybody uses their OS for. (except big companies for proprietary stuff). Good the zfs code could become better through more devs but therefor the users that use bsd would go down drastically from a very low point already.
The only thin foiled hat thing I could think of is that they would see it as reason to split the Linux community and weaken the Linux marketing / progression with that

Every one that wants it in Linux sounds to me like a guy that says please I hate BSD so much let me use it in Linux that I don't have to use bsd anymore, but that might be my fantasies.

But yes I see no reason to use openzfs this target audience the enterprises wouldn't they use just the oracle stuff that is newer and better? Why use the amateur fork? It's for me like guy that goes to schools and gives a small dosage of drug for free to the children then later they will get the hard stuff from Oracle

You know, you "linux-lover" (Yeah, I can be equally sneeringly derogatory), I won't mind personally. ZoL will never be "fully integrated". CDDL/GPL2 conflict does not allow it. It's permissible on BSD though.

Due to being out of tree, ZoL is going to be under much tighter constraints than ZoF and will forever face more issues, leaving enough advantages to BSD - while retaining compatibility. ZoF does not have to deal with dkms nor find ways around if kernel devs decide to break/lose something they'd need. Title of this article is just one of examples fitting the pattern.

[starshipeleven]

KVM/QEMU can be developed without redhat

so does Virtualbox

[starshipeleven]

Let's freeze this hate train a second and point out that the application does not need to ask the kernel to use AES-NI or any other CPU instruction directly, which is what it should have been doing all along.

(OpenSSH for example does it, so does OpenVPN)

[starshipeleven]

Redhat software is intentionally badly designed, implemented, buggy, difficult use and slow. Examples: gnome3,pulseaudio,systemd,networkmanager and polkit. Virtualbox works fine when the vbox driver compiles with your kernel.

The only "intentionally badly designed, implemented, buggy, difficult use and slow" in that list is GNOME3, and it would still be a stretch. It's not THAT bad.

[starshipeleven]

It seems like this removal was simply made out of spite against people who were using ZFS and for no other reason.

It was all clearly described in the commit that removed it, it was deprecated for a long while and then the last module using this interface stopped using it.

[Britoid]

Redhat software is intentionally badly designed, implemented, buggy, difficult use and slow. Examples: gnome3,pulseaudio,systemd,networkmanager and polkit. Virtualbox works fine when the vbox driver compiles with your kernel.

Virtualbox is far inferior to KVM/QEMU. What the fuck are you talking about.

[oiaohm]

It seems like this removal was simply made out of spite against people who were using ZFS and for no other reason.

I would not say so. The reworked functions are using RCU and other known patent techs in ways they were not before. That is interesting problem is there a issue there or is there not.