From: Andrew Morton <akpm@osdl.org>
To: ltuikov@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched.h: increment TASK_COMM_LEN to 20 bytes
Date: Fri, 30 Jun 2006 18:37:44 -0700 [thread overview]
Message-ID: <20060630183744.310f3f0d.akpm@osdl.org> (raw)
In-Reply-To: <20060701012658.14951.qmail@web31803.mail.mud.yahoo.com>
Luben Tuikov <ltuikov@yahoo.com> wrote:
>
> > We do occasionally hit task_struct.comm[] truncation, when people use
> > "too-long-a-name%d" for their kernel thread names. But we seem to manage.
>
> It would be especially helpful if you want to name a task thread
> the NAA IEEE Registered name format (16 chars, globally unique), for things
> like FC, SAS, etc. This way you can identify the task thread with
> the device bearing the NAA IEEE name.
>
> Currently just last character is cut off, since TASK_COMM_LEN is 15+1.
>
> 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.
next prev parent reply other threads:[~2006-07-01 1:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-01 1:06 [PATCH] sched.h: increment TASK_COMM_LEN to 20 bytes Luben Tuikov
2006-07-01 1:19 ` Andrew Morton
2006-07-01 1:26 ` Luben Tuikov
2006-07-01 1:37 ` Andrew Morton [this message]
2006-07-01 2:48 ` Luben Tuikov
2006-07-01 4:46 ` Jeff Garzik
2006-07-01 4:53 ` Andrew Morton
2006-07-07 17:00 ` Luben Tuikov
2006-07-07 17:10 ` Jeff Garzik
2006-07-09 0:48 ` Luben Tuikov
2006-07-01 9:01 ` Jan Engelhardt
2006-07-03 12:07 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2006-06-24 2:27 Albert Cahalan
2006-06-23 16:49 Luben Tuikov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060630183744.310f3f0d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltuikov@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox