nanook

As I expected, it got bounced over to Intel and the basic response was it’s not ready yet.

@CameronDev @thingsiplay I refer you to this: https://www.pubnub.com/blog/how-fast-is-realtime-human-perception-and-technology/

That said, we did an experiment in a physics class many years ago where by there was a beeper and an electromagnet that were powered by the same source. The electromagnet held a yard stick in place. When the beeper went off we were supposed to push a button in response. The button stopped the fall of the yardstick. Then by calculating how far the yard stick fell using the 32m/s^2 speed of gravitational acceleration we calculated how long response was, average was about 200ms, I responsed in 30ms, however this only works for me for auditory queues, visual is more delayed for me, and I can’t detect any change in under 20ms and just barely at that, let alone respond to it. But what I learned in that class was that reaction times varied individual to individual by a factor of about ten, so what is true for one person may not be for another.

@thingsiplay @CameronDev I agree consistent delay is better because your brain automatically adjusts for it, it has several hundred milliseconds of delay built-in, but inconsistent sub-millisecond delay is not going to be humanly detectable.

@CameronDev @thingsiplay As I previously stated, a normal preemptive kernel will generally provide <1ms latency. RT does provide the possibility of lower latency and not inconsistent as you suggest unless you are resource saturated.

The 6.12 kernel UHD630 graphics worked when not compiled for realtime but just voluntary preemption. So I have filed Bug 219510. I suspect the kernel team will refer me to Intel since they actually maintain this driver, then Intel will say well it worked when the kernel people didn’t hack it for real time and it will end up going nowhere but time will tell. Without a working display, I can’t really test KVM/QEMU so will have to wait for action on this bug.

@thingsiplay @recursive_recursion

With respect to gaming, the answer is a definite “maybe”. Here is the thing with a real time kernel, context switching is expensive, and especially so when going between kernel and userland mode. This is because you have to save/restore all the registers on the stack so there are a lot of memory cycles involved in a context switch. A realtime kernel increases context switching a LOT so you’re going to eat more CPU than you otherwise would but on the other hand, critical things will get attended to in a more timely manner. So whether the latency or the overall computational efficiency is more important will make the difference in gaming. Also to some degree hardware, most games will only use 4 cores or so, a few more than that but most only about 4, so if you’ve got an 18 core machine, you have plenty of core for the extra kernel overhead, it is more likely to benefit than if you’re on a 4-core machine with all the cores already saturated.

@thingsiplay @lemmy.ca A normal preemptive kernel with 1000HZ tick will usually provide sub 1ms latency which for most audio is adequate.

That said, I just built 6.12.0 and the display drivers for UHD630 graphics appear to be broken, at least when compiled for realtime. I am going to go re-compile it normal pre-emptive as I normally do and see if it has the same issues. It booted, and got up to the point where it executed /etc/rc.local because it turned on my keyboard leds, but the screen never displayed.

If you wish to try I have built for both debian and redhat based systems, you can download the install packages, .deb or .rpm at:
https://www.eskimo.com/kernel/linux-6.12-tickless/realtime/

@recursive_recursion I am building now.

I’ve avoided RT thus far because it was incompatible with KVM/QEMU. Am curious if this is still the case. Guess I can compile and install on my workstation and see
if my virtual machines still work.

@Codilingus @strawberry You can pass through your physical audio device then let pipewire on the hypervisor do it.

Yes it is possible and it works just fine.

What I ran in my Linksys WRT54G was DD-WRT, it provided all the normal functionality sans the occasional lockups the stock firmware did, and in addition you could attach to other networks, you could participate in a mesh network, you could increase the transmitter power from 7mw up to as much as 100mw (and this really helped in my environment).

@JoMiran @zShxck That is very nice. I love the way you can toggle between disk space usage and disk I/O usage. Here is a btop of the machine that friendica.eskimo.com is running on:

I’ve got a Gigabyte X299 Aorus Master with i9-10980xe overclocked at 4.8Ghz, two nvme drives mounted on the motherboard, this is about the most power hungry consumer level CPU you can get (maxes at around 540 watts), yet the ssd’s which are also fairly heavily used in a database, only run at about 29C. Perhaps your GPU is heating up your SSDs? I have no active cooling on mine either, just the cheesy heat sinks. I’m running 6.11.2, unfortunately 6.11 kernels past two have some code that breaks the i9-10980xe so stuck at that for the moment.

@Sheldan Yes I am referring to the game, back when I had tried on vmware it was still the main commercial one that I was playing, I have since moved to Insanity Flyff. One of those minor continuities in my life.

@ouch @WhiteOakBayou If you try to remove essential packages, it will not allow you without an extra flag, even as root.

@Magister @WhiteOakBayou There are a lot of things to like about MX, nice interface, I really like that you can boot up using either systemd or sys-V, since systemd tends to be a lot faster but also tends to break it makes it really nice to have a sys-v fallback when things do break. Support has been excellent, I’ve yet to have it take them more than three days to fix anything broken I’ve reported, contrast that with Ubuntu where if it happens within the next three major releases you’re doing good.

To be sure, the base install of debian is a everything and the kitchen sink install. There are MANY package the average person is not going to need.

Single GPU isn’t substantially harder than 2GPU pass through, that is what I have done, but it does require support by the UEFI bios and the GPU and not all support it.

@brian I have used it and with flyff at least the performance was far insuperior to kvm/qemu.