Thank you. I guess the interesting question here is whether current SCHED_OTHER behavior makes sense for majority of usecases (or any, really).
I think current situation makes isolcpus unusable in at least one common case - when user want to isolate some critical multithreaded application e.g. benchmark. Usually it's not desirable to add some custom scheduling logic to such program (e.g. source code may not even be available). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2116749 Title: Thread affinity broken under isolcpus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2116749/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
