| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
The patch no longer applies because the default elevator initalisation
has been refactored a bit[1] in kernel 5.4.
Content-wise our patch is still the same.
[1]: https://github.com/torvalds/linux/commit/a0958ba7fcdc316e3900f8d2afda519850d60985
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
| |
This option was removed in Linux 5.0, so let's make its absence
non-fatal for the build of the config.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
| |
Since kernel 4.20, the option no longer exists and it's enabled
unconditionally.
So in order to stay backwards-compatible with older kernels, let's only
enable that option if it actually exists (thus the "?").
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
| |
The patch got posted to the LKML a while ago and a better[1] patch[2]
eventually got into stable, so we can safely drop the patch on our end.
[1]: https://lore.kernel.org/patchwork/patch/959862/#1191565
[2]: https://patchwork.kernel.org/patch/10668441/
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
I now experienced the crash for the second time whenever my machine
starts swapping. The details about the crash(es) and the corresponding
fix can be found at:
https://bugs.chromium.org/p/chromium/issues/detail?id=822360
When the patch lands in mainline and stable, we can revert this very
commit.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
| |
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
| |
Even though these options are rather opinionated rather than generally
useful, it makes sense to have an option for that because I'm going to
use it for my managed machines as well.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
| |
The patch no longer applies with this kernel version because the patch
context has changed.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
| |
The patch for <= 4.14 no longer applies, because elevator_get() now has
an additional argument.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
| |
The change dropping the SCSI_MQ_DEFAULT option has been reverted in
torvalds/linux@cbe7dfa26eee4819db7b5846181d56fd0cece0ea, so while the
release canidate versions didn't have this option, the final release
however does have it again.
So we need to wait until 4.14 for it to become removed hopefully.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
| |
This has been removed upstream and is no longer needed, see commit
torvalds/linux@5c279bd9e40624f4ab6e688671026d6005b066fa.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This dissolves the user.aszlig.system.kernel module, which was not only
to stay on the latest bleeding edge kernel but also to enable BFQ. The
latter has been factored out already a while ago already.
Originally, I had a fully custom kernel config for mmrnmhrm and dnyarri,
but it's no longer the case and thus the user.aszlig.system.kernel
module is now no longer needed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
Not everybody likes to have the latest release canidate kernel, so we
now have an option called vuizvui.system.kernel.bfq.enable, which *only*
enables the BFQ scheduler per default.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell
|
