SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 30 | April | 2000 ]

<< Previous Message <<


Date: Sun, 30 Apr 2000 16:08:42 PST
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: OS/2 as real-time OS ?

Content Type: text/plain

Steven Levine wrote:
>
> I've been involved in some aerospace stuff.
> ... The inner loops where invariably analog.

Yup. Analog works!

> The DSP we used was capable of implementing a 50
> block control loop with several filters in 800 uSec.

I sense a topic for a future Programming SIG ...

> Ideally you want to write as much of the application
> as possible in ring 3. This requires context switches.
> My understanding is that the OS/2 scheduler will not
> guarantee a context switch to even the highest
> priority process in much less than [1 msec].

So stay out of ring 3. :)))

If it's to be a "real-time" system, there's no reason why the real-time
portion can't stay in ring 0.

> >Hah, you got me. What is a "context hook"?
>
> You know those DDK books you misplaced...

Me? Misplace something?

> A context hook allows an interrupt handler to schedule
> part of itself to run at task time (i.e. just before the
> scheduler would return control to an interrupted
> process). This code is interruptible, so it can do the
> work it needs without holding off other pending interrupts.

Let me go and review the header code ...

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message <<

Return to [ 30 | April | 2000 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.