Package Details: linux-ck 6.11.10-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base: linux-ck
Description: The Linux kernel and modules with ck's hrtimer patches
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 459
Popularity: 0.23
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-26 13:15 (UTC)

Dependencies (14)

Required by (7)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 68 69 70 71 72 73 74 75 76 77 78 .. 308 Next › Last »

graysky commented on 2017-08-15 21:20 (UTC) (edited on 2017-08-15 21:25 (UTC) by graysky)

@mrkline - Interesting... I get the same. EDIT: https://ck-hack.blogspot.com/2017/08/linux-412-ck2-muqss-version-0160-for.html?showComment=1502832329876#c3067299809122898386

mrkline commented on 2017-08-15 20:20 (UTC)

Scratch that, 4.12.7-2 seems to have the same issue.

mrkline commented on 2017-08-15 18:40 (UTC)

Apparently ck-2 contains changes to make BFQ the default scheduler: http://ck-hack.blogspot.com/2017/08/linux-412-ck2-muqss-version-0160-for.html So we should be good to go as soon as @graysky bumps this.

vp1981 commented on 2017-08-15 12:32 (UTC) (edited on 2017-08-15 12:36 (UTC) by vp1981)

@mrkline, you may ask post-factum to translate new on linux.org.ru, see https://www.linux.org.ru/news/kernel/13581989, but this is receipt from the news: [russian] Планировщики ввода-вывода при использовании blk-mq нельзя указывать через командную строку ядра в загрузчике. Вместо этого используйте правило udev, например: ACTION=="add|change", KERNEL=="sd[a-z]*", ATTR{queue/scheduler}="bfq" Чтобы включить подсистему blk-mq, ядро нужно собрать с опцией CONFIG_SCSI_MQ_DEFAULT=y или передать параметр scsi_mod.use_blk_mq=1 из загрузчика. [/russian] (my translation) ... use udev rule, for example: ACTION=="add|change", KERNEL=="sd[a-z]*", ATTR{queue/scheduler}="bfq" In order to enable blk-mq subsystem the kernel has to be configured with option CONFIG_SCSI_MQ_DEFAULT=y or pass parameter scsi_mod.use_blk_mq=1 in boot loader. P.S. Gee, I found the news on post-factum site: https://pf.natalenko.name/news/, see "v4.12-pf2 is out" (https://pf.natalenko.name/news/?p=291)

mrkline commented on 2017-08-15 07:27 (UTC) (edited on 2017-08-15 07:36 (UTC) by mrkline)

@graysky 4.12.7-1 boots and runs fine on several of my boxen. The only curious tidbit is that even though BFQ is set as the default: $ zcat /proc/config.gz | grep -i BFQ CONFIG_DEFAULT_BFQ=y CONFIG_DEFAULT_IOSCHED="bfq" CONFIG_IOSCHED_BFQ=y CONFIG_BFQ_GROUP_IOSCHED=y The kernel is defaulting to mq-deadline: $ cat /sys/block/sda/queue/scheduler [mq-deadline] kyber bfq none Is this what @kwe was discussing below? EDIT: See https://groups.google.com/d/msg/bfq-iosched/j4QUK4IPOhw/CY1LmmhcAwAJ What's the simplest way to switch all disks to BFQ on boot in the meantime?

artafinde commented on 2017-08-15 06:49 (UTC) (edited on 2017-08-15 07:29 (UTC) by artafinde)

Building 4.12.7-1. Apart for the changes in config so you have to configure lots more than before we are missing the CPU optimizations. Update: Got a non-bootable kernel. Trying a second build, config seems better now as expected (I'll blame ccache which I disabled now). #2 Update: Non bootable again, stuck at "Triggering udevents"

pedrogabriel commented on 2017-08-15 02:03 (UTC)

4.12.7-1 works like a charm.

kwe commented on 2017-08-14 19:58 (UTC)

@graysky That config option will disappear in the future because the behavior will be enabled by default: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi?id=5c279bd9e40624f4ab6e688671026d6005b066fa&h=master Apparently this is planned for 4.13: linux/drivers/scsi$ git tag --contains 5c279bd9e40624f4ab6e688671026d6005b066fa v4.13-rc1 v4.13-rc2 v4.13-rc3 v4.13-rc4 v4.13-rc5 So, when it comes around, you might want to remove it again. :)

beest commented on 2017-08-14 19:25 (UTC)

4.12.7-1 boots, everything seems kosher so far.

graysky commented on 2017-08-14 18:31 (UTC)

@zebulon - Please try 4.12.7-1 which contains a suggestion by CK to fix. Does it boot and run? I cannot build and test for some time.

« First ‹ Previous 1 .. 68 69 70 71 72 73 74 75 76 77 78 .. 308 Next › Last »