public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dean Nelson <dcn@sgi.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mingo@elte.hu, linux-ia64@vger.kernel.org, linux-altix@sgi.com,
	edwardsg@sgi.com, linux-kernel@vger.kernel.org, akpm@osdl.org,
	anton.wilson@camotion.com
Subject: Re: [PATCH] MAX_USER_RT_PRIO and MAX_RT_PRIO are wrong!
Date: Tue, 7 Jun 2005 15:19:49 -0500	[thread overview]
Message-ID: <20050607201949.GA11013@sgi.com> (raw)
In-Reply-To: <1118172182.4972.4.camel@localhost.localdomain>

On Tue, Jun 07, 2005 at 03:23:02PM -0400, Steven Rostedt wrote:
> On Tue, 2005-06-07 at 14:10 -0500, Dean Nelson wrote:
> 
> > I just built and tested a kernel and xp/xpc/xpnet modules with your patch
> > applied. It ran fine. The priorities of the xpc kthreads were correct.
> > 
> > Looks good to me.
> 
> Dean, 
> 
> If you can do me a favor, the way you really want to test this is by
> changing MAX_USER_RT_PRIO to 99 and MAX_RT_PRIO to 
> (MAX_USER_RT_PRIO+1).  This will make sure that the patch is working.
> Your kernel thread should still run at priority 99. 
> 
> Check it with:  ps -eo pid,rtprio,comm
> 
> And grep for your thread name.

Just did as you asked and things seem fine. Ran on an SGI altix.
(The first process shown below shouldn't have a priority of 99,
just the others.)

cranberry5:~ # ps -eo pid,rtprio,comm | grep xpc
13325      - xpc_hb
13327     99 xpc08
13467     99 xpc06
13469     99 xpc06c1
13501     99 xpc06c1
13502     99 xpc06c1
cranberry5:~ #


      reply	other threads:[~2005-06-07 20:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07  2:46 [PATCH] MAX_USER_RT_PRIO and MAX_RT_PRIO are wrong! Steven Rostedt
2005-06-07  3:25 ` Steven Rostedt
2005-06-07  5:33 ` Ingo Molnar
2005-06-07 11:25   ` Steven Rostedt
2005-06-07 15:48     ` Dean Nelson
2005-06-07 17:31       ` Steven Rostedt
2005-06-07 19:10         ` Dean Nelson
2005-06-07 19:23           ` Steven Rostedt
2005-06-07 20:19             ` Dean Nelson [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=20050607201949.GA11013@sgi.com \
    --to=dcn@sgi.com \
    --cc=akpm@osdl.org \
    --cc=anton.wilson@camotion.com \
    --cc=edwardsg@sgi.com \
    --cc=linux-altix@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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