=== brainwash_ is now known as brainwash
[03:09] <White_Light> is there any documentation on the performance effects of having CONFIG_LOCK_STAT enabled, with /proc/sys/kernel/lock_stat set to 0
[08:11] <apw> White_Light, not that i am aware of
[10:25] <mamarley> apw: It looks like the mainline build for 4.16.8 again failed: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.8/
[10:29] <apw> mamarley, bah, bloody upstream changing the kernel makefile ABI
[10:29] <apw> "kconfig: rename silentoldconfig to syncconfig"
[10:30] <mamarley> Yeah, that seems ill-advised for a point release…
[10:30] <apw> no this is because 4.16 does not have it, but 4.17 does, which is where the packaging is coming from
[10:30] <mamarley> Ah, OK.
[10:30] <apw> but really upstream, a pox on you
[10:30] <apw> mamarley, that is going to take a bit to work around
[10:31] <mamarley> No problem, I will just run by own build.
[10:31] <mamarley> s/by/my
=== mamarley is now known as Guest24421
=== mamarley_ is now known as mamarley
[13:00] <White_Light> apw, but I'm guessing that performance is the reason CONFIG_LOCK_STAT is not set on stock ubuntu kernel configs?
[13:00] <apw> White_Light, that is highly likely
[13:00] <apw> though we would have evaluated it most likely at the time it was first added and not since
[13:02] <White_Light> I see
[13:03] <White_Light> thanks for your help, I appreciate you guys having this public channel
[13:03] <apw> it is the ubuntu way :)
[13:04] <apw> we try and be transparent in the main
=== rsalveti is now known as rsalveti__
=== rsalveti__ is now known as rsalveti
=== brainwash_ is now known as brainwash