[lkml]   [2013]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH tip/core/rcu 05/14] rcu: Distinguish "rcuo" kthreads by RCU flavor
On Sat, Jan 05, 2013 at 09:48:55AM -0800, Paul E. McKenney wrote:
> From: "Paul E. McKenney" <>
> 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

 \ /
  Last update: 2013-01-07 18:41    [W:1.123 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site