Package Details: linux-ck 6.12.1-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.24
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-23 13:58 (UTC)

Dependencies (14)

Required by (6)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 106 107 108 109 110 111 112 113 114 115 116 .. 308 Next › Last »

graysky commented on 2016-10-07 00:07 (UTC)

@jwhickman - Dunno about NUMA. Have to ask some users to test and verify that it is or is not a problem. Anyone willing to test? Also, I don't think MuQSS is stable at this point. We'll probably have BFS until the 4.9 release if I read CK's blog correctly. In either case, the linux-ck brand is here to stay; MuQSS will still have the ck1 brand as I understand it.

jwhickman commented on 2016-10-06 12:52 (UTC) (edited on 2016-10-06 12:58 (UTC) by jwhickman)

Thanks @graysky! I modified this to build MQS for k4.8; no problems besides having to comment out the BFQ patches due to a compile failure, not unsurprisingly. I was hoping the k4.7 BFQ patches would work on k4.8, since the patches applied without issue. :) Question for you; is the 'NUMA disable issue' still relevant, as it's been around a long time, plus now this is MQS. Also, I noticed in my k4.8 build, the config showed a new tick rate of 250 Hz, so was also curious about that. /======================================================= # Running with a 1000 HZ tick rate (vs the ARCH 300) is reported to solve the issues with the bfs/linux 3.1x and suspend. [...] _1k_HZ_ticks=y ### Do not disable NUMA until CK figures out why doing so causes panics for some users! [...] #_NUMAdisable= =======================================================/ In commented original discussion on the tick rate, ck has said, "(16 September 2013 at 18:55) If it still needs 1000Hz to work correctly, then there is still a bug." Anyway, thanks again!

graysky commented on 2016-10-06 09:05 (UTC)

OK... unofficial patches. I was wondering if something was in the merge queue on the topic that I didn't see.

zerophase commented on 2016-10-06 09:03 (UTC)

@graysky These patches https://github.com/damige/linux-nvme

graysky commented on 2016-10-06 08:58 (UTC)

What patches are you referring to?

zerophase commented on 2016-10-06 03:15 (UTC)

Anyone know if the Linux-nvme kernel patches have any issues with ck? Going to be picking up an nvme drive in a couple week and just want to check if anyone knows of any issues.

graysky commented on 2016-10-05 18:09 (UTC)

@Pedrogabriel - Yes, if you enable the build option. I just updated 4.7.6-1 to pull in MuQSS v106 (disabled by default).

pedrogabriel commented on 2016-10-05 15:45 (UTC)

Does MuQSS 106 apply to 4.7?

graysky commented on 2016-10-04 22:12 (UTC)

105 is out but it's jacked up and does not cleanly apply to either 4.7 or 4.8. See CK's latest blog. I have unflagged; please flag again when the 105 is updated.

pedrogabriel commented on 2016-10-04 22:00 (UTC)

MuQSS 105 is out now.

« First ‹ Previous 1 .. 106 107 108 109 110 111 112 113 114 115 116 .. 308 Next › Last »