slay -P problem (6.2.1)

<!doctype html public “-//w3c//dtd html 4.0 transitional//en”>

If I try to slay -P my driver process, nothing happens, the priority stays the same.
(e.g. slay -P 25 mrt-drvr)
I'm logged in as root.

The application is a port from QNX4.25 where the command
is given in software, and works fine there.

I'm able to adjust other processes' prioities in 6.2.1.
What would make this driver behave this way?
 

Drivers generally float to the priority of the process that
communicates with them (or the interrupt pulse) so setting
the priority would only last until the next interrupt
or message.

acellarius@yahoo.com wrote:

!doctype html public “-//w3c//dtd html 4.0 transitional//en”
html
If I try to slay -P my driver process, nothing happens, the priority stays
the same.
br>(e.g. slay -P 25 mrt-drvr)
br>I’m logged in as root.
p>The application is a port from QNX4.25 where the command
br>is given in software, and works fine there.
p>I’m able to adjust other processes’ prioities in 6.2.1.
br>What would make this driver behave this way?
br> </html


cburgess@qnx.com

Yes, by default in QNX6 every connection is priority float.

acellarius@yahoo.com wrote:

!doctype html public “-//w3c//dtd html 4.0 transitional//en”
html
So is this a difference between QNX4 & 6?
br>The driver process is just a MsgReceive loop processing either
br>a timer event or a message from a GUI process.
br>I wasn’t expecting it’s priority to change at all once run, except
br>via something like slay.
p>PS sorry about the HTML droppings in that previous message…
p>Colin Burgess wrote:
blockquote TYPE=CITE>Drivers generally float to the priority of the process
that
br>communicates with them (or the interrupt pulse) so setting
br>the priority would only last until the next interrupt
br>or message.</blockquote
/html


cburgess@qnx.com

<!doctype html public “-//w3c//dtd html 4.0 transitional//en”>

So is this a difference between QNX4 & 6?
The driver process is just a MsgReceive loop processing either
a timer event or a message from a GUI process.
I wasn't expecting it's priority to change at all once run, except
via something like slay.

PS sorry about the HTML droppings in that previous message...

Colin Burgess wrote:

Drivers generally float to the priority of the process that
communicates with them (or the interrupt pulse) so setting
the priority would only last until the next interrupt
or message.

How can I can get the process to run at a fixed priority?
It is launched by a Photon process using spawn.
The slay command was used in QNX4 to make it run
at the higher priority.

Colin Burgess wrote:

Yes, by default in QNX6 every connection is priority float.

acellarius@yahoo.com wrote:
ayc > How can I can get the process to run at a fixed priority?
ayc > It is launched by a Photon process using spawn.
ayc > The slay command was used in QNX4 to make it run
ayc > at the higher priority.

ayc > Colin Burgess wrote:

Yes, by default in QNX6 every connection is priority float.

If it is a process that you wrote, then set the priority yourself.
I.E. SchedSet()

If it is a QNX process, then they are all writtne to priority float.
So they will run at the priority of the last message that they
received or the highest priority of the messages in it’s message
queue.


Bill Caroselli – Q-TPS Consulting
qtps@earthlink.net

Hi Bill
thanks, I will give it a try.

Bill Caroselli wrote:


If it is a process that you wrote, then set the priority yourself.
I.E. SchedSet()

If it is a QNX process, then they are all writtne to priority float.
So they will run at the priority of the last message that they
received or the highest priority of the messages in it’s message
queue.