Package Details: linux-ck-headers 6.11.10-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base: linux-ck
Description: Headers and scripts for building modules for Linux-ck kernel
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL-2.0-only
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 458
Popularity: 0.154155
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-26 13:15 (UTC)

Latest Comments

« First ‹ Previous 1 .. 61 62 63 64 65 66 67 68 69 70 71 .. 308 Next › Last »

kwe commented on 2017-11-04 20:10 (UTC)

@Terence Deadline should be an option: $ cat /sys/block/sda/queue/scheduler mq-deadline kyber [bfq] none

Terence commented on 2017-11-04 20:09 (UTC)

@kwe Ok, I'm indeed using grub and forgot about that, thanks. One more question: I have my root partition on my SSD and my home/var partition on my HDD. I was before using deadline on the SSD and BFQ on the HDD. It seems I can't do that anymore now and it's confirmed by the arch wiki. Will it's still perform ok with the SSD compared to deadline or is there another alternative for my system configuration?

kwe commented on 2017-11-04 20:02 (UTC)

@Terence: From what I can tell, the "elevator" parameter is being slowly phased out and might only set the sq scheduler. Using elevator=[mq-scheduler] seems to crash. There is a patch for the Linux kernel that fixes this crash by introducing a relevant check, but it won't be introduced until 4.15 IIRC. You don't need to boot a live system if you're using GRUB. You can edit the start parameters via the E key and then fix your GRUB config from within your normal system.

Terence commented on 2017-11-04 19:58 (UTC)

@kwe Thanks for your relevant comment, I tried to use the 'elevator' kernel parameter but it crashed the kernel at boot and I needed to boot to the live usb to be able to fix it. I then have 2 questions: 1) Why are there still patches for BFQ included? 2) Can the package be updated with "CONFIG_SCSI_MQ_DEFAULT = y"?

kwe commented on 2017-11-04 18:59 (UTC)

@everybody who is not involved, @Terence I've had some troubles figuring out what's up, so here is my tl;dr of the issue: We used to have BFQ as a part of the ck kernel patches. With a recent kernel version, you have BFQ merged into the vanilla kernel.org kernel tree. Hence, BFQ was removed from the ck patchset. However, the BFQ in the kernel is for blk-mq, whereas previously we had bfq for non-mq / sq. Because this kernel defaults to sq (CONFIG_SCSI_MQ_DEFAULT = n), the mq BFQ from the Linux kernel is not available. The solution seems to be to either build with that option enabled or alternatively boot the kernel with scsi_mod.use_blk_mq=1

Terence commented on 2017-11-04 18:52 (UTC)

I can't get BFQ to be enabled with the latest version.

keepitsimpleengr commented on 2017-10-31 20:37 (UTC)

@graysky got it

graysky commented on 2017-10-31 19:29 (UTC)

@keepitsimp - It's due to the fact that nvidia-utils-387.22-1 is out but I know and thus didn't update nvidia-ck. It has been done now. In the future please flag the nvidia-ck package out-of-date.

mrkline commented on 2017-10-31 18:04 (UTC)

Apparently I'm blind and/or need more coffee. My apologies.

sir_lucjan commented on 2017-10-31 17:49 (UTC)

@mrkline # Patch source with ck patchset patch -Np1 -i "../${_ckpatchname}" patch -Np1 -R -i "../0015-Enable-and-make-BFQ-default-IO-scheduler-overriding-.patch" patch -Np1 -i "../unfuck_bfq_v2.patch" Do you see "patch -R" or not?

« First ‹ Previous 1 .. 61 62 63 64 65 66 67 68 69 70 71 .. 308 Next › Last »