Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1646858

Core isolation, cpu hotplug and stop_machine

Show all headers | View raw

Hello,

As I understand it the recommended way to force pending timers of a
core when trying to isolate it (runtime) is to use cpu hotplug. The
current implementation of cpu hotplug has a serious drawback in that
it uses stop_machine() which disturbs already isolated cores. This is
a serious problem in our usecase.

I would guess we are not the only ones with this problem, but as far
as I can see there is currently no solution for this in the latest
next. There was a patchset back in 2013 that implemented
stop_machine-free hotplug, but that was never accepted.
(https://lwn.net/Articles/538819/)

So is there any ongoing work to solve this problem and what is the
preferred way to solve it, is it:

1) stop_machine() free hotplug. It seems to be quite complex but
probably solves more problems
    then the one above.
2) Invent some new mechanism/interface separate from hotplug to
migrate timers and hrtimers.
3) Don't, because this isn't a use-case that linux should support.

/Fredrik

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Core isolation, cpu hotplug and stop_machine Fredrik Markström <fredrik.markstrom@gmail.com> - 2017-05-22 15:10 +0200
  Re: Core isolation, cpu hotplug and stop_machine Thomas Gleixner <tglx@linutronix.de> - 2017-05-22 21:10 +0200

csiph-web