| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] Interrupt levels
> > This can happen if you block/unblock very frequently. The timer
> > interrupt from Xen isn't entirely tick-based -- you also
> get a timer
> > interrupt every time you are rescheduled.
>
> By block/unblock I assume you mean context switching between different
> domains. Is this level normal? Is there a method to track down exactly
> is causing the block/unblocking?
>
> > So the large number of timer interrupts indicates lots of
> unblocking.
> > Really we should hold-off the timer interrupt if the domain was
> > descheduled for less than a jiffy. :-)
>
> Is there a way to fix this at the moment?
Since processing timer interrupts are cheap there's no urgent fix
required.
The real question is why are you blocking/unblocking at a rate of
55k/second.
What are your domains doing? What interrupt rates do they see?
Ian
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
|
|
| |
|
Home