Li Qiang wrote:
> Currently, the default maximum CPU throttle for migration is
> 99(CPU_THROTTLE_PCT_MAX). This is too big and can make a remarkable
> performance effect for the guest. We see a lot of packets latency
> exceed 500ms when the CPU_THROTTLE_PCT_MAX reached. This patch set
> adds a
* Li Qiang (liq...@gmail.com) wrote:
> Hello Dave,
>
> What's status of this patch, Do you gonna merge it?
Yes, once 3.1 opens.
Dave
> Thanks,
> Li Qiang
>
>
> 2018-08-02 18:47 GMT+08:00 Dr. David Alan Gilbert :
>
> > * Li Qiang (liq...@gmail.com) wrote:
> > > Currently, the default
Hello Dave,
What's status of this patch, Do you gonna merge it?
Thanks,
Li Qiang
2018-08-02 18:47 GMT+08:00 Dr. David Alan Gilbert :
> * Li Qiang (liq...@gmail.com) wrote:
> > Currently, the default maximum CPU throttle for migration is
> > 99(CPU_THROTTLE_PCT_MAX). This is too big and can
* Li Qiang (liq...@gmail.com) wrote:
> 2018-08-02 18:47 GMT+08:00 Dr. David Alan Gilbert :
>
> > * Li Qiang (liq...@gmail.com) wrote:
> > > Currently, the default maximum CPU throttle for migration is
> > > 99(CPU_THROTTLE_PCT_MAX). This is too big and can make a remarkable
> > > performance
2018-08-02 18:47 GMT+08:00 Dr. David Alan Gilbert :
> * Li Qiang (liq...@gmail.com) wrote:
> > Currently, the default maximum CPU throttle for migration is
> > 99(CPU_THROTTLE_PCT_MAX). This is too big and can make a remarkable
> > performance effect for the guest. We see a lot of packets latency
* Li Qiang (liq...@gmail.com) wrote:
> Currently, the default maximum CPU throttle for migration is
> 99(CPU_THROTTLE_PCT_MAX). This is too big and can make a remarkable
> performance effect for the guest. We see a lot of packets latency
> exceed 500ms when the CPU_THROTTLE_PCT_MAX reached. This
Currently, the default maximum CPU throttle for migration is
99(CPU_THROTTLE_PCT_MAX). This is too big and can make a remarkable
performance effect for the guest. We see a lot of packets latency
exceed 500ms when the CPU_THROTTLE_PCT_MAX reached. This patch set
adds a new max-cpu-throttle
