Re: [PATCH tip/core/rcu 05/14] rcu: Distinguish "rcuo" kthreads byRCU flavor

From: Josh Triplett
Date: Mon Jan 07 2013 - 11:54:45 EST

On Sat, Jan 05, 2013 at 09:48:55AM -0800, Paul E. McKenney wrote:
> From: "Paul E. McKenney" <paul.mckenney@xxxxxxxxxx>
> Currently, the per-no-CBs-CPU kthreads are named "rcuo" followed by
> the CPU number, for example, "rcuo". This is problematic given that

I think the quoted string on this second line wanted to have a CPU
number in it.

> there are either two or three RCU flavors, each of which gets a per-CPU
> kthread with exactly the same name. This commit therefore introduces
> a one-letter abbreviation for each RCU flavor, namely 'b' for RCU-bh,
> 'p' for RCU-preempt, and 's' for RCU-sched. This abbreviation use used
> to distinguish the "rcuo" kthreads, for example, for CPU 0 we would have
> "rcuo0b", "rcuo0p", and "rcuo0s".

Don't per-CPU kthreads normally have a name ending in /$cpunum ?, rather
than just $cpunum? For instance, kworker/0, kworker/1, and so on?
Seems like these threads should follow that convention.

- Josh Triplett
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at