public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Ankit Jain <ankitjain1580@yahoo.com>,
	linux <linux-kernel@vger.kernel.org>
Subject: Re: Difference in priority
Date: Mon, 11 Oct 2004 22:43:15 +1000	[thread overview]
Message-ID: <416A7FE3.8090106@kolivas.org> (raw)
In-Reply-To: <416A7E25.8050101@kolivas.org>

Con Kolivas wrote:
> Ankit Jain wrote:
> 
>> hi
>>
>> if somebody knows the difference b/w /PRI of both
>> these commands because both give different results
>>
>> ps -Al
>> & top
>>
>> as per priority rule we can set priority upto 0-99
>> but top never shows this high priority
> 
> 
> Priority values 0-99 are real time ones and 100-139 are normal 
> scheduling ones. RT scheduling does not change dynamic priority while 
> running wheras normal scheduling does (between 100-139). top shows the 
> value of the current dynamic priority in the PRI column as the current 
> dynamic priority-100. If you have a real time task in top it shows as a 
> -ve value. ps -Al seems to show the current dynamic priority+60.

That should read dynamic priority-60 in the PRI column.

Cheers,
Con

  reply	other threads:[~2004-10-11 12:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-11 12:17 Difference in priority Ankit Jain
2004-10-11 12:35 ` Con Kolivas
2004-10-11 12:43   ` Con Kolivas [this message]
2004-10-12  9:28     ` Ankit Jain
2004-10-12 10:40       ` Con Kolivas
  -- strict thread matches above, loose matches on Subject: below --
2004-10-12  0:57 Albert Cahalan
2004-10-13  0:15 ` Con Kolivas
2004-10-13  1:17   ` Albert Cahalan
2004-10-13  1:26     ` Con Kolivas
2004-10-13  4:58     ` Lee Revell
2004-10-13  5:08       ` Randy.Dunlap
2004-10-13  5:39         ` Lee Revell

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=416A7FE3.8090106@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=ankitjain1580@yahoo.com \
    --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