Linus Torvalds writes: (Summary) The rcu_call() part fundamentally will happen on any CPU,
and sure, it could then schedule the work on something else, but that
doesn't sound like a particularly sound interface.
doesn't sound like a particularly sound interface.
So I'd like to either just make the thing always just use WORK_CPU_UNBOUND, or hear some kind of (handwaving ok) explanation for why something else would ever make sense. If the action is fundamentally delayed by RCU, why would it make a difference which CPU it runs on?
it runs on?
One reason for that is that I get this feeling that the multiple stages of waiting *might* be unnecessary.
doesn't sound like a particularly sound interface.
So I'd like to either just make the thing always just use WORK_CPU_UNBOUND, or hear some kind of (handwaving ok) explanation for why something else would ever make sense. If the action is fundamentally delayed by RCU, why would it make a difference which CPU it runs on?
it runs on?
One reason for that is that I get this feeling that the multiple stages of waiting *might* be unnecessary.