Slashdot Mirror

← Back to Stories (view on slashdot.org)

Interview With Chris McKillop of QNX

Posted by timothy on from the three-little-letters dept.

Sheepish writes "OSNews features an interview with Chris McKillop, software engineer of QNX Software Systems. Chris, the most outspoken and 'visible' QNX employee in the QNX community, is discussing about performance differences between RT and monolithic kernels, the difficulties of pitching a new OS to the world, the Linux and Microsoft threat to QNX in the embedded space, QNX's Momentics desktop operating system and more."

4 of 22 comments (clear)

  1. Chris is very active on supporting the community. by qnx6 · · Score: 5, Informative

    If you read the QNX community site, you will see that cdm is very active in the forums, answering questions from QNX users. For the other QNX employees that do "say" something, the number of posts are far behind. cdm is also "full time" on the #qnx irc channel at irc.qnxstart.com. Drop by if you wanna say hi to him :)

  2. It's QNX Neutrino by variable · · Score: 5, Informative

    QNX Momentics is our development toolset - it exists on Windows, Solaris and Neutrino. The "desktop" OS is actually QNX Neutrino.

    --
    ........ "The faster I go, the behinder I get" - Lewis Carroll
  3. Re: It is NOT spyware by Anonymous Coward · · Score: 2, Informative

    This is just a new form of advertising, it only works on IE 5.5 and above. So, it seems that you are using IE... ;-)

  4. That's simple by Anonymous Coward · · Score: 3, Insightful
    It's a real time OS. It has hard realtime requirements. Lets say the program that is supposed to respond to an interrupt is swapped out. Then the hard realtime requirement has to include the maximum latency for seeking the disk head, the maximum rotational delay, plus all the regular overhead.


    Right now, it's a context switch. They have a well measured, well defined maximum time it takes to do a context switch. Depends on the machine, but it's absolutely consistant, and documented what the worst case is, on the 386's we used for an embedded system it was well under 10 milliseconds (the regular quantum of the QNX 4.2).

    I want to say it was on the order of microseconds. It was very, very fast.

    The other problem, is that swapping, and virtual memory create a whole new realm of non-repeatable test cases. It's complicates the OS, and the testing of the groups of applications a great deal. QNX is supposed to run in pace makers, the NASA shuttles, fuel injections systems, and all kinds of other places, where "Opps, guess we never hit that case in testing, call the Q/A team, or e-mail the mailing list to find a resolution", isn't acceptable. QNX is incredibly simple, well defined, and acts the same way all the time. That's the beauty of it. Swap is a horrible abberation, that greatly complicates the systems, and introduces whole new classes of bugs, races, priority inversions. Just all kinds of nastyness, which is completely acceptable on a desktop OS, and not at all acceptable on a RTOS.


    Kirby