[Autogenerated] Once an inter app service routine cues the D PC.
It goes into a queue, that is managed by a processor.
So D PC Q,
is just a list of PCs to be processed process being needing
to run those call backs those functions.
That are stored within the D PC there, is one such QE per processor,
and usually a processor takes care of its own PCs D,
PCs that have been queued, to that current processor.
However, it is possible for one processor,
to help another processor, to process, these D,
PCs faster.
For example, suppose you have two processors.
One of them, is very busy processing.
PCs and the other is completely idle doing nothing.
So the idea processor might wake up in order to process,
D, PCs and help out with just running those functions as quickly as possible.
The purpose of these D, PCs is to run some code usually after an interrupt,
service routine, and It's important.
To Let them run as soon as possible.
And Of course, they're running an our Q,
two always so implicitly, their are ordered just like a normal.
First in first out ques possible, to tweak,
these things little bit using some a _ _ _,
the kernel provides but generally they are going to be
handled in the first in first out basis.
And essentially.
What does it mean?
To handle, the PCs simply calling function,
and arguments, and As I mentioned already several times,
the most common usage of D, PCs is providing the ability,
to do certain operations which either cannot be done within the
internet up service routine such as calling OLE requests or doing
certain things which are not very important.
To do during the I S R.
And it's better.
To use something which is less powerful.
And lower URL when performing these operations in a lower URL
setting the function behind the scenes.
That handles, that DPC Q,
is called K I retire DPC list which is an internal function
within the kernel Let's see if we can figure out or get a sense
of what happens when these DPC S, are actually running