From: Robert Love <rml@tech9.net>
To: alan@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4-ac: real-time / scheduling information out of /proc
Date: 19 Sep 2002 17:29:40 -0400 [thread overview]
Message-ID: <1032470981.20929.171.camel@phantasy> (raw)
In-Reply-To: <1032470788.16889.169.camel@phantasy>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
On Thu, 2002-09-19 at 17:26, Robert Love wrote:
> The attached patch exports scheduling policy and real-time priority from
> /proc/<pid>/stats.
>
> Support for reading this information is in procps CVS.
>
> This information has been in 2.5 since 2.5.18.
>
> It does not break old versions of procps as it just adds the new entries
> to the end. I do not know what the practice is wrt adding proc fields
> in stable kernels, however since this does not break procps, is
> supported by current procps, and is in 2.5 -- it is perfectly safe to
> me.
>
> Patch is against 2.4.20-pre7-ac3, please apply.
Ugh, missing a comma. Sorry,
Robert Love
[-- Attachment #2: proc-add-rt-info-rml-2.4.20-pre7-ac3-1.patch --]
[-- Type: text/x-patch, Size: 725 bytes --]
diff -urN linux-2.4.20-pre7-ac3/fs/proc/array.c linux/fs/proc/array.c
--- linux-2.4.20-pre7-ac3/fs/proc/array.c Thu Sep 19 16:10:34 2002
+++ linux/fs/proc/array.c Thu Sep 19 17:18:36 2002
@@ -346,7 +346,7 @@
read_unlock(&tasklist_lock);
res = sprintf(buffer,"%d (%s) %c %d %d %d %d %d %lu %lu \
%lu %lu %lu %lu %lu %ld %ld %ld %ld %ld %ld %lu %lu %ld %lu %lu %lu %lu %lu \
-%lu %lu %lu %lu %lu %lu %lu %lu %d %d\n",
+%lu %lu %lu %lu %lu %lu %lu %lu %d %d %lu %lu\n",
task->pid,
task->comm,
state,
@@ -389,7 +389,9 @@
task->nswap,
task->cnswap,
task->exit_signal,
- task_cpu(task));
+ task_cpu(task),
+ task->rt_priority,
+ task->policy);
if(mm)
mmput(mm);
return res;
prev parent reply other threads:[~2002-09-19 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 21:26 [patch] 2.4-ac: real-time / scheduling information out of /proc Robert Love
2002-09-19 21:29 ` Robert Love [this message]
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=1032470981.20929.171.camel@phantasy \
--to=rml@tech9.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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