assembly kod

[HWSW Famulus]

az MSDN idezet csak! azt, mondja, hogy
a lenyegtelen oprendszer funkciokat
(eger, disk flush) is kepes blokkolni a 31-es prioritas mivel
azok alacsonyabb prioritassal futnak ennel.

Ettol meg az utemezo muxik es utemez is, ha van mit!
Lasd 3 esetet amikor utemezes kovetkezik.....
Nomeg muxik a memoria manager a security rendszer es millio mas szal is

KJ

> > Ne bosszants mar......
> >
> > Most roviden, de mindjart hosszan is megkapod az infot......
> >
> > Utemezni meg a timecritical azaz 31-es prioritasu szala(ka)t is utemezni
> > kell
> > Ettol preemptive egy oprendszer!!!!!!
> >
> > Vagyis nem a futo szal dont mikor engedi el a CPU-t,
> > (ilyen volt valaha pl. 3.1-es win)  hanem az utemezo mindig
> > elveszi amikor az idokvantum lejar.....
> > aztan legfeljebb visszadja, ha nincs jobb otlete :-)
> >
> > ---------------------------------------
> > The scheduler must make !!!!!! a CPU scheduling decision every
time!!!!!!!!
> > one of three
> > situations occurs:
> >
> > * A thread's quantum on the CPU expires.
> > * A thread waits for an event to occur.
> > * A thread becomes ready to execute.
> >
> > When a thread's quantum expires, the scheduler executes the
FindReadyThread
> > algorithm to decide whether another thread needs to take over the CPU.
If a
> > higher-priority thread is ready to execute, it replaces (or preempts)
the
> > thread that was running.
> > --------------------------
> >
> > KJ
> >
> >
> Ezek az idezetek az MSDN-bol valok!
>
> High priority indicates a process that performs time-critical tasks
requiring
> immediate execution for it to run correctly. The threads of a
high-priority class
> process preempt the threads of normal or idle priority class processes. An
example
> is the Windows Task List, which must respond quickly when called by the
user,
> regardless of the load on the operating system. Use extreme care when
using the
> high-priority class, because a high- priority class CPU-bound application
can use
> almost all available cycles.
>
> You should almost never use REALTIME_PRIORITY_CLASS, because this
interrupts system
> threads that manage mouse input, keyboard input, and background disk
flushing. This
> class can be appropriate for applications that "talk" directly to hardware
or that
> perform brief tasks that should have limited interruptions.
>
> The Realtime priority indicates a process that has the highest possible
priority.
> The threads of a real-time priority class process preempt the threads of
all other
> processes, including operating system processes performing important
tasks. For
> example, a real-time process that executes for more than a very brief
interval can
> cause disk caches not to flush or cause the mouse to be unresponsive. This
priority
> should almost never be used.
>
> Zoli
>
>
>
>