I am developing a real time application that has problems with the Network
Manager interrupting it. The application that I am developing does not
require the Network Manager to have a high priority.
How do I lower the priority of the Network Manager?
How do you know it’s the Network manager that is disrupting
your program???
It’s much better to raise your own program above Net then to lower
Net.
“Alan Larson” <wintec@wintec-inc.c om> wrote in message
news:8rl51t$1v8$1@inn.qnx.com…
I am developing a real time application that has problems with the Network
Manager interrupting it. The application that I am developing does not
require the Network Manager to have a high priority.How do I lower the priority of the Network Manager?
Here is some more background to the problem.
About two years ago my coworkers developed an application under QNX 4.23
that had some problems with the response time. After investigating the
problem they discovered that the Network Manager had a priority that was too
high for this specific application. They solved the problem by recompiling
QNX with a lower priority Network Manager.
Recently we upgraded QNX to version 4.25. The upgrade process restored the
Network Manager to its original priority, and the response time problem is
occurring again. Also, the person that originally solved the problem has
left the company.
I need to repeat the same work that my coworker did two years ago. Any
information that QNX can supply on the topic would be very helpful. Also,
if there are any new features that allow the priority to be set when Net
Manager starts that would be helpful too.
“Mario Charest” <mcz@videotron.ca> wrote in message
news:8roc6h$rhu$1@inn.qnx.com…
How do you know it’s the Network manager that is disrupting
your program???It’s much better to raise your own program above Net then to lower
Net.“Alan Larson” <> wintec@wintec-inc.c > om> wrote in message
news:8rl51t$1v8$> 1@inn.qnx.com> …
I am developing a real time application that has problems with the
Network
Manager interrupting it. The application that I am developing does not
require the Network Manager to have a high priority.How do I lower the priority of the Network Manager?
\
I would be very surprise if the problem is related to Net.
Net priority floats to that of the client that makes request.
Actually if you look at the documentation of Net you
will see that it is highly recommended NOT to change
priority of Net or it’s driver.
I suspect what you need to do is to change to priority
of Proc32 (core of the OS). In order to do this you must
rebuild (not recompile) the image file. With 4.25 that image
is in /boot/build/install.
Edit that file and add -P 26 do the second line where Proc32 is
specify.
Now to rebuild the image
cd/boot/build
make b=install.
Then copy the resulting file:
cp /boot/build/images/install.<…> /.boot
Then reboot
Upon reboot if you do a sin, you should see priority
of Proc32 is 26. Make sure your process runs at priority
higher then 26 and you should be all set!!!
“Alan Larson” <alan_lawson@wintec-inc.c om> wrote in message
news:8rskp7$9ha$1@inn.qnx.com…
Here is some more background to the problem.
About two years ago my coworkers developed an application under QNX 4.23
that had some problems with the response time. After investigating the
problem they discovered that the Network Manager had a priority that was
too
high for this specific application. They solved the problem by
recompiling
QNX with a lower priority Network Manager.Recently we upgraded QNX to version 4.25. The upgrade process restored
the
Network Manager to its original priority, and the response time problem is
occurring again. Also, the person that originally solved the problem has
left the company.I need to repeat the same work that my coworker did two years ago. Any
information that QNX can supply on the topic would be very helpful. Also,
if there are any new features that allow the priority to be set when Net
Manager starts that would be helpful too.“Mario Charest” <> mcz@videotron.ca> > wrote in message
news:8roc6h$rhu$> 1@inn.qnx.com> …How do you know it’s the Network manager that is disrupting
your program???It’s much better to raise your own program above Net then to lower
Net.“Alan Larson” <> wintec@wintec-inc.c > om> wrote in message
news:8rl51t$1v8$> 1@inn.qnx.com> …
I am developing a real time application that has problems with the
Network
Manager interrupting it. The application that I am developing does
not
require the Network Manager to have a high priority.How do I lower the priority of the Network Manager?
\
Mario,
On my system Net appears to run 23r (Round Robin). Proc
on the other hand runs 30f (Float).
As far as “recompiling” there is no way for a user to
recompile Net. One simple way to change the behavior of
Net would be to do the following:
This will change the priority of Net.
There may also be a programatic way to do this.
Previously, Mario Charest wrote in comp.os.qnx:
I would be very surprise if the problem is related to Net.
Net priority floats to that of the client that makes request.
Actually if you look at the documentation of Net you
will see that it is highly recommended NOT to change
priority of Net or it’s driver.I suspect what you need to do is to change to priority
of Proc32 (core of the OS). In order to do this you must
rebuild (not recompile) the image file. With 4.25 that image
is in /boot/build/install.<node numberEdit that file and add -P 26 do the second line where Proc32 is
specify.Now to rebuild the image
cd/boot/build
make b=install.<node numberThen copy the resulting file:
cp /boot/build/images/install.<…> /.bootThen reboot
Upon reboot if you do a sin, you should see priority
of Proc32 is 26. Make sure your process runs at priority
higher then 26 and you should be all set!!!“Alan Larson” <> alan_lawson@wintec-inc.c > om> wrote in message
news:8rskp7$9ha$> 1@inn.qnx.com> …
Here is some more background to the problem.
About two years ago my coworkers developed an application under QNX 4.23
that had some problems with the response time. After investigating the
problem they discovered that the Network Manager had a priority that was
too
high for this specific application. They solved the problem by
recompiling
QNX with a lower priority Network Manager.Recently we upgraded QNX to version 4.25. The upgrade process restored
the
Network Manager to its original priority, and the response time problem is
occurring again. Also, the person that originally solved the problem has
left the company.I need to repeat the same work that my coworker did two years ago. Any
information that QNX can supply on the topic would be very helpful. Also,
if there are any new features that allow the priority to be set when Net
Manager starts that would be helpful too.“Mario Charest” <> mcz@videotron.ca> > wrote in message
news:8roc6h$rhu$> 1@inn.qnx.com> …How do you know it’s the Network manager that is disrupting
your program???It’s much better to raise your own program above Net then to lower
Net.“Alan Larson” <> wintec@wintec-inc.c > om> wrote in message
news:8rl51t$1v8$> 1@inn.qnx.com> …
I am developing a real time application that has problems with the
Network
Manager interrupting it. The application that I am developing does
not
require the Network Manager to have a high priority.How do I lower the priority of the Network Manager?
\
–
Mitchell Schoenbrun --------- maschoen@pobox.com
“Mitchell Schoenbrun” <maschoen@pobox.com> wrote in message
news:Voyager.001009115206.1195A@schoenbrun.com…
Mario,
On my system Net appears to run 23r (Round Robin). Proc
on the other hand runs 30f (Float).Yes my mistake, however even if Proc priority floats there
are thing that it does on it’s own.
As far as “recompiling” there is no way for a user to
recompile Net. One simple way to change the behavior of
Net would be to do the following:slay -P ## Net
According to the doc, this can be dangerous.
This will change the priority of Net.
There may also be a programatic way to do this.
setprio() 
Previously, Mario Charest wrote in comp.os.qnx:
I would be very surprise if the problem is related to Net.
Net priority floats to that of the client that makes request.
Actually if you look at the documentation of Net you
will see that it is highly recommended NOT to change
priority of Net or it’s driver.I suspect what you need to do is to change to priority
of Proc32 (core of the OS). In order to do this you must
rebuild (not recompile) the image file. With 4.25 that image
is in /boot/build/install.<node numberEdit that file and add -P 26 do the second line where Proc32 is
specify.Now to rebuild the image
cd/boot/build
make b=install.<node numberThen copy the resulting file:
cp /boot/build/images/install.<…> /.bootThen reboot
Upon reboot if you do a sin, you should see priority
of Proc32 is 26. Make sure your process runs at priority
higher then 26 and you should be all set!!!“Alan Larson” <> alan_lawson@wintec-inc.c > om> wrote in message
news:8rskp7$9ha$> 1@inn.qnx.com> …
Here is some more background to the problem.
About two years ago my coworkers developed an application under QNX
4.23
that had some problems with the response time. After investigating
the
problem they discovered that the Network Manager had a priority that
was
too
high for this specific application. They solved the problem by
recompiling
QNX with a lower priority Network Manager.Recently we upgraded QNX to version 4.25. The upgrade process
restored
the
Network Manager to its original priority, and the response time
problem is
occurring again. Also, the person that originally solved the problem
has
left the company.I need to repeat the same work that my coworker did two years ago.
Any
information that QNX can supply on the topic would be very helpful.
Also,
if there are any new features that allow the priority to be set when
Net
Manager starts that would be helpful too.“Mario Charest” <> mcz@videotron.ca> > wrote in message
news:8roc6h$rhu$> 1@inn.qnx.com> …How do you know it’s the Network manager that is disrupting
your program???It’s much better to raise your own program above Net then to lower
Net.“Alan Larson” <> wintec@wintec-inc.c > om> wrote in message
news:8rl51t$1v8$> 1@inn.qnx.com> …
I am developing a real time application that has problems with the
Network
Manager interrupting it. The application that I am developing
does
not
require the Network Manager to have a high priority.How do I lower the priority of the Network Manager?
\Mitchell Schoenbrun --------- > maschoen@pobox.com
“Mitchell Schoenbrun” <maschoen@pobox.com> wrote in message
news:Voyager.001009115206.1195A@schoenbrun.com…
Mario,
On my system Net appears to run 23r (Round Robin). Proc
on the other hand runs 30f (Float).
Isn’t that 30f (Fifo)?
Marty
Previously, Marty Doane wrote in comp.os.qnx:
Mario,
On my system Net appears to run 23r (Round Robin). Proc
on the other hand runs 30f (Float).Isn’t that 30f (Fifo)?
Well now that you mention it, I’m not %100 sure. On the
other hand, what would Proc FIFO against?
Mitchell Schoenbrun --------- maschoen@pobox.com
“Marty Doane” <doanemr@REMOVE_rapistan.com> wrote in message
news:8rv3s6$o2n$1@inn.qnx.com…
“Mitchell Schoenbrun” <> maschoen@pobox.com> > wrote in message
news:> Voyager.001009115206.1195A@schoenbrun.com> …
Mario,On my system Net appears to run 23r (Round Robin). Proc
on the other hand runs 30f (Float).Isn’t that 30f (Fifo)?
Yes, my mistake, float flag is shown via “sin flags”, and Net doesn’t float
…!
Marty