SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Wind River going up, up, up!

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Ronald Paul who wrote (5067)4/27/1999 1:15:00 PM
From: Prognosticator  Read Replies (1) of 10309
 
VxWorks is not only hard: it is lean and scalable across a whole range of devices with different peripherals. CE is a heavyweight by comparison. VxWorks adds a lot of value even when an embedded device does not have a user-interface integrated into the hardware, Windows CE can't claim the same utility: it is after all... Windows. I don't think VxWorks and Windows CE do compete in the same arena, there is really no need for them to do so either.

Any embedded developer who is thinking about using Windows CE should take a careful look at the priority mechanisms built into the Windows CE Kernel (http://www.microsoft.com/WindowsCE/developer/resources/techpapers/realtime.asp). CE gives you a whopping 8 FIXED priority levels for threads, compared with 256 DYNAMIC in VxWorks. 8 really isnt enough to run a system: once you assign priority levels for exception handlers, network drivers, and other operations, there isn't much left for the real work of the device. CE is at least simpler than the terrible mess they came up with in NT, where thread and process priorities interact in random ways to try and load balance the system for you so you can't know when a thread will execute.

Corrections and elaborations welcome.

P.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext