> > > config HZ
> > > int
> > > - default 100 if HZ_100
> > > + default 100 if HZ_100 || XEN
> > > default 250 if HZ_250
> > > default 1000 if HZ_1000
> > >...
> >
> > Why?
>
> Because the hypervisor sends timer interrupts to the guest at a rate
> of 100 Hz while the guest is running. We might add support to have
> an adjustable rate in the future but so far 100 Hz has worked quite
> well for us.
It seems to me that a guest should be telling a hypervisor how
frequently it needs a timer interrupt, not vice versa. And
it should be possible for different guests to have different HZ.
Given all the lkml debate on HZ over the last few years
and the compromise solution (configurable HZ_nnn), forcing
100 Hz on the guest appears to be a step backwards.
(BTW, Xen/ia64 honors all guest's configured HZ.)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
