You cant change the UM design but you can change the OS? You can also change the UM code enough to use interlocked loops instead of events? Hmmm - This is an odd combination of constraints
Based on the extremely vague requirements, I agree with Anton ? Windows is probably a bad choice for you. The IO model does not really match the way you are thinking about the problem.
Assuming that you persist in this, and don?t care about killing the overall machine performance, effectively hijacking cores by running threads with realtime priority in tight loops is a reasonably reliable way to get what you want.
I reiterate that this is a poor design in any OS, but I digress.
Sent from Mailhttps: for Windows 10
From: xxxxx@gmail.commailto:xxxxx
Sent: June 21, 2017 2:49 PM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: RE:[ntdev] Notifying user mode applications of a device interrupt without a DPC
Thanks to everyone for all the feedback. To reiterate, I don’t have the luxury of changing the design of notifying a UM app of the interrupt, so I’m attempting the interlocked flag pattern. I have a feeling this will have its own set of problems, so I may end up giving up and recommending a different OS.
—
NTDEV is sponsored by OSR
Visit the list online at: http:
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:
To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:></http:></mailto:xxxxx></mailto:xxxxx></https:>