Messages in this thread | | | Date | Sat, 1 Jul 2006 11:01:42 +0200 (MEST) | From | Jan Engelhardt <> | Subject | Re: [PATCH] sched.h: increment TASK_COMM_LEN to 20 bytes |
| |
>> >> I think incrementing it would be a good thing, plus other things >> may want to represent 8 bytes as a character array to be the name >> of a task thread. > >OK, that's a reason. Being able to map a kernel thread onto a particular >device is useful. > Eh, that is not the case for some ATM.
Do "migration", "ksoftirqd", "watchdog", "events", "kblockd" and "aio" map to a particular device besides possibly "CPU"?
"xfslogd", "xfsdatad", and "rpciod" also have one thread per CPU rather than per-device or per-mount.
"pdflush" even has a variable number of threads running, depending on load. One thread may serve many mounts/devices, or - I have seen this - eight instances manage two mounts.
Jan Engelhardt -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |