|| ||Steven Rostedt <email@example.com> |
linux-rt-users <firstname.lastname@example.org> |
|| ||[RFC][PATCH RT 0/4 v2] sched/rt: Lower rq lock contention latencies on many CPU boxes |
|| ||Wed, 12 Dec 2012 14:27:33 -0500|
|| ||Thomas Gleixner <email@example.com>,
Carsten Emde <C.Emde@osadl.org>,
John Kacur <firstname.lastname@example.org>,
Peter Zijlstra <email@example.com>,
Clark Williams <firstname.lastname@example.org>,
Ingo Molnar <email@example.com>,
Frank Rowand <firstname.lastname@example.org>,
Mike Galbraith <email@example.com>|
|| ||Article, Thread
This version I rearranged the patches a little so that the IPI patch
comes last. As the first 3 patches are less controversal, and should
probably be added now.
The difference in this version was that I added more comments, but
more importantly I also added a sched feature called RT_PUSH_IPI.
When this feature is enabled, it switches the pull logic to send
an IPI to the RT overloaded CPU to do a push instead of doing the
When the feature is disabled, the push/pull logic stays the same as
it always has (with rq lock contention).
Now I've discussed this with Clark, and we noticed that the contention
didn't show up until we tried it on a 24 CPU machine. On a 16 CPU machine
it ran fine. Thus, by default, machines with 16 or less CPUs will
have the RT_PUSH_IPI feature disabled. Machines with 17 or more
possible CPUs will have the feature enabled at boot up. Note, we haven't
tried it on a machine with 17 to 23 CPUs.
It is safe to enable or disable this feature at run time, although
you may cause latencies in doing so, but there shouldn't be any missed
wakeups or anything else that is serious. The worse that can happen
is that you miss a pull, and an RT task will stay on its CPU when it
could have migrated to another CPU that just lowered its priority.
Well, if you are worried about that, don't change it when you care :-)
The 16 CPUs is just a heuristic, and people may debate it. And perhaps
you may not like how the push/pull default changes between different
machines. I could also add a command line switch to force enable/disable
at boot, and/or I could add a config as well.
Right now, by default <= 16 CPU machines are as it always was, and
17 or more CPU machines have this new logic enabled. Either one can
change it at run time via the debugfs directory (unfortunately it's
not a sysctl).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/