Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

The QNX Operating System


September 1991/The QNX Operating System/Sidebar

Update: Quantum Releases A Posix Compliant Version Of QNX


In June 1991, Quantum started shipping QNX v4.0. This new version of their operating system is POSIX compliant — at least as far as is possible — as not all of the areas of the POSIX standard have been completed and ratified.

The term POSIX stands for Portable Operating System Interface and refers to a group of standards that are being developed under the auspices of the IEEE. The POSIX standard is actually a group of proposed standards which encompass the following areas:

1003.1 System Interface
1003.2 Shell and Utilities
1003.3 Test Methods
1003.4 Real Time
1003.5 Ada Bindings
1003.6 POSIX Security
1003.7 System Admin
1003.8 POSIX Networking
1003.9 FORTRAN Bindings

The purpose of IEEE's POSIX is to provide an industry standard operating system environment which is based on the UNIX operating system.

An important point is that POSIX is not an implementation of an operating system and its environment, it is a definition. This allows operating system vendors to produce POSIX compliant systems which "look" similar to both the programmer and user, but which may be quite different as far as their internal architecture, performance, etc.. It is this flexibility which allowed Quantum to produce an operating system which is both POSIX compliant and which also takes special advantage of their message passing, client-server based architecture.

First Impressions Of QNX 4.0

Since I have only recently obtained QNX 4.0, I am not in a position to review it. Hence, the following is merely a brief summary of my first impressions of Quantum's new operating system.

As well as POSIX compliance, Quantum appears to have made many significant improvements in the following areas:

  • v4.0 is even more "modular" than v2.15 (only the operating system processes that are needed on a given node need to be running).
  • Task/process scheduling of equal priority tasks has been improved and can be tailored on a per process basis. Scheduling of multiple processes that have equal priority and which are ready can be done by FIFO, round robin, or adaptive (priority decay) methods.
Note: Higher priority processes always immediately pre-empt a lower priority process, regardless of scheduling methods used — essential for real-time systems.

  • Server processes can request that messages be received in time order or priority order.
  • Server processes no longer have to run at fixed priority levels. They may choose to have their priority dynamically adjusted. This change is significant in that it eliminates the priority inversion problem which could "bushwack" the unwary real time system designer using v2.15.
  • The native C-Compiler for QNX 4.0 is WATCOM C.
  • A number of inter-task communication methods have been added and the signal_port and (software) port mechanism have been enhanced.
  • The QNX shell complies with the IEEE POSIX standard. (This is very similar to the AT&T System V shell.)
  • File system performance appears to have been significantly increased due to a complete redesign.
These, and many other changes are beyond the scope of the present article. What is clear, is that QNX 4.0 has not been re-written just to comply with POSIX standards, it has been re-written for the purpose of enhancing its real-time performance as well. How well this has been achieved would be a good topic for a follow up article.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.