From: Steven Rostedt <rostedt@goodmis.org>
To: Dean Nelson <dcn@sgi.com>
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, 07 Jun 2005 19:23:02 +0000 [thread overview]
Message-ID: <1118172182.4972.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20050607191001.GA8768@sgi.com>
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.
Thanks,
-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Dean Nelson <dcn@sgi.com>
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, 07 Jun 2005 15:23:02 -0400 [thread overview]
Message-ID: <1118172182.4972.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20050607191001.GA8768@sgi.com>
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.
Thanks,
-- Steve
next prev parent reply other threads:[~2005-06-07 19:23 UTC|newest]
Thread overview: 15+ 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 11:25 ` Steven Rostedt
2005-06-07 15:48 ` Dean Nelson
2005-06-07 15:48 ` Dean Nelson
2005-06-07 17:31 ` Steven Rostedt
2005-06-07 17:31 ` Steven Rostedt
2005-06-07 19:10 ` Dean Nelson
2005-06-07 19:10 ` Dean Nelson
2005-06-07 19:23 ` Steven Rostedt [this message]
2005-06-07 19:23 ` Steven Rostedt
2005-06-07 20:19 ` Dean Nelson
2005-06-07 20:19 ` Dean Nelson
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=1118172182.4972.4.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=akpm@osdl.org \
--cc=anton.wilson@camotion.com \
--cc=dcn@sgi.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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.