From: Arjan van de Ven <arjan@infradead.org>
To: Vladimir Zapolskiy <vz@mleia.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] sched: share task comm length value to userspace
Date: Mon, 5 Sep 2011 12:47:26 -0700 [thread overview]
Message-ID: <20110905124726.28b24db4@infradead.org> (raw)
In-Reply-To: <1315247881-31597-1-git-send-email-vz@mleia.com>
On Mon, 5 Sep 2011 21:38:01 +0300
Vladimir Zapolskiy <vz@mleia.com> wrote:
> This change allows to get a defined length of task comm in
> userspace. For a moment this value is implied at least in two cases:
> * max length of comm value got from /proc/$pid/stat
> * max string length argument of prctl(PR_[SG]ET_NAME, ...)
>
> For these reasons it becomes desirable to impart task comm max length
> value to userspace.
I'm sorry but I don't like doing this.
The moment we do this, we never can increase it anymore since userspace
might be using it for its own uses and we'd break it if we changed
this value.
If we need to export this, we should export it in /proc or /sys
somewhere as a dynamic value.....
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2011-09-05 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 18:38 [PATCH] sched: share task comm length value to userspace Vladimir Zapolskiy
2011-09-05 19:47 ` Arjan van de Ven [this message]
2011-09-05 20:17 ` Vladimir Zapolskiy
2011-09-05 20:39 ` Arjan van de Ven
2011-09-09 23:41 ` Andrew Morton
2011-09-09 23:49 ` Andrew Morton
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=20110905124726.28b24db4@infradead.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=vz@mleia.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