On Mon, 8 Oct 2018 at 20:04, Liran Alon wrote:
>
>
>
> > On 8 Oct 2018, at 13:59, Wanpeng Li wrote:
> >
> > On Mon, 8 Oct 2018 at 05:02, Liran Alon wrote:
> >>
> >>
> >>
> >>> On 28 Sep 2018, at 9:12, Wanpeng Li wrote:
> >>>
> >>> From: Wanpeng Li
> >>>
> >>> In cloud environment, lapic_timer_
> On 8 Oct 2018, at 13:59, Wanpeng Li wrote:
>
> On Mon, 8 Oct 2018 at 05:02, Liran Alon wrote:
>>
>>
>>
>>> On 28 Sep 2018, at 9:12, Wanpeng Li wrote:
>>>
>>> From: Wanpeng Li
>>>
>>> In cloud environment, lapic_timer_advance_ns is needed to be tuned for
>>> every CPU
>>> generations
On Mon, 8 Oct 2018 at 05:02, Liran Alon wrote:
>
>
>
> > On 28 Sep 2018, at 9:12, Wanpeng Li wrote:
> >
> > From: Wanpeng Li
> >
> > In cloud environment, lapic_timer_advance_ns is needed to be tuned for
> > every CPU
> > generations, and every host kernel versions(the
> > kvm-unit-tests/tscde
> On 28 Sep 2018, at 9:12, Wanpeng Li wrote:
>
> From: Wanpeng Li
>
> In cloud environment, lapic_timer_advance_ns is needed to be tuned for every
> CPU
> generations, and every host kernel versions(the
> kvm-unit-tests/tscdeadline_latency.flat
> is 5700 cycles for upstream kernel and 96
On 28/09/2018 08:12, Wanpeng Li wrote:
> From: Wanpeng Li
>
> In cloud environment, lapic_timer_advance_ns is needed to be tuned for every
> CPU
> generations, and every host kernel versions(the
> kvm-unit-tests/tscdeadline_latency.flat
> is 5700 cycles for upstream kernel and 9600 cycles for
From: Wanpeng Li
In cloud environment, lapic_timer_advance_ns is needed to be tuned for every
CPU
generations, and every host kernel versions(the
kvm-unit-tests/tscdeadline_latency.flat
is 5700 cycles for upstream kernel and 9600 cycles for our 3.10 product kernel,
both preemption_timer=N, S
6 matches
Mail list logo