Package Details: linux-ck 6.11.7-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.32
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-09 16:45 (UTC)

Dependencies (14)

Required by (6)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 70 71 72 73 74 75 76 77 78 79 80 .. 307 Next › Last »

JunioCalu commented on 2017-07-16 11:37 (UTC)

About P6_NOPS, should I enable it?

graysky commented on 2017-07-13 22:34 (UTC)

@gnu - done, will be in the next update, thks

beest commented on 2017-07-13 15:02 (UTC)

Just for the sake of pedantry, next release you may want to change the URL preceding _BFQ_enable_ to https://wiki.archlinux.org/index.php/Improving_performance#Tuning_IO_schedulers as the fragment in the original comment is dead and the linux-ck page links there now anyway.

r08 commented on 2017-07-11 20:35 (UTC)

@QuartzDragon @artafinde Thanks for the feedback. I guess I'm not the only one... Will test this using CONFIG_HZ_PERIODIC=y to see if I get the same latency issues..

artafinde commented on 2017-07-09 07:17 (UTC) (edited on 2017-07-09 07:30 (UTC) by artafinde)

@QuartzDragon: I have similar behaviour with my laptop here (Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz). I was setting the tick to 1000Hz before MuQSS but on the first iterations of MuQSS I think it was better. Do you get same freezes with linux from core? Is it fixed if you compile your own -ARCH and set tick to 1000Hz?

QuartzDragon commented on 2017-07-08 22:38 (UTC)

When I change CONFIG_HZ to 1000, CONFIG_HZ_100_MUQSS seems to be automatically unset.

artafinde commented on 2017-07-08 08:57 (UTC) (edited on 2017-07-08 08:57 (UTC) by artafinde)

MuQSS 0.150 reverted the Hz back to 100Hz and I think that's the recommended value from ck. @QuartzDragon, r08 do you change both the below: CONFIG_HZ_100_MUQSS=y CONFIG_HZ=100

graysky commented on 2017-07-08 07:37 (UTC)

@Quartz and r08 - Post to ck's blog?

QuartzDragon commented on 2017-07-08 06:54 (UTC) (edited on 2017-07-08 06:55 (UTC) by QuartzDragon)

In the past, I too had noticed weird stuttering using 100Hz, so now I always set it to 1000Hz. System is smooth. :)

r08 commented on 2017-07-07 10:51 (UTC)

Interesting how I noticed slow downs using the default MuQSS@100Hz while using Firefox and running Steam games like Team Fortress 2. Setting it to 1000Hz fixed the latency issues I was having. Should 1000Hz tick be the recommended setting for a "normal desktop user?" Running old Intel Core 2 T9500@2.60Ghz

« First ‹ Previous 1 .. 70 71 72 73 74 75 76 77 78 79 80 .. 307 Next › Last »