Obviously, yenta_socket is causing this behavior.
After a few tests it appears that loading yenta_socket makes the number of wake ups jump to 6K/s, but unloading it then reloading it reset the number of wakeups to a standard value.
Obviously, yenta_socket is causing this behavior.
After a few tests it appears that loading yenta_socket makes the number of wake ups jump to 6K/s, but unloading it then reloading it reset the number of wakeups to a standard value.