Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

Using Dos for Real Time applications -> CLI (Developers)

posted by Damien, 27.12.2012, 23:23

> > Most likely it's the timer interrupt called every cca 18.2 ms (!!!) and
> > eating more time than usual cca every 1 second.
> >
> > > Is this avoidable ?
> >
> >
> >   CLI
> >

>
> Yes the most of time can take BIOS/DOS interrupts. But even if you CLI,
> there will occur some SMM interrupts that are handled by SMI handler and
> cannot be disabled (this is transparrent and running behind all OS). BIOS
> writers should make this routines as fast as possible but it still may take
> some us or maybe tens of us? It also depends on hardware config and BIOS.
> If you need some microsecond precision timing I rather suggest to connect
> some external microcontroller to do this job.

Hello,

Concerning CLI I don't really know how to do it, I guess it's inline assembler in my C-code ? Also my problem is that I don't want to inhibit all interrupts at the same time but one by one, to see which one is the origin of this "long" 400us task...

Moreover, I have tested my little "loop program" on another computer, older. And the surprise is that this 400usec task does not happen. There is indeed some fluctuation, but all the loops take less that 50usec.
To sum up, this phenomenon depends on hardware used, or maybe bios options...

 

Complete thread:

Back to the forum
Board view  Mix view
22762 Postings in 2122 Threads, 402 registered users (1 online)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum