[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANRm+Cw7tg1=2CFua8-FOuJGPXdkRbgNNBOtGSoz1iJWuxXK2g@mail.gmail.com>
Date: Wed, 24 Jan 2018 16:07:57 +0800
From: Wanpeng Li <kernellwp@...il.com>
To: Mike Galbraith <efault@....de>
Cc: linux-kernel@...r.kernel.org, kvm <kvm@...r.kernel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Radim Krcmar <rkrcmar@...hat.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: unixbench context switch perfomance & cpu topology
2018-01-23 21:49 GMT+08:00 Mike Galbraith <efault@....de>:
> On Tue, 2018-01-23 at 18:36 +0800, Wanpeng Li wrote:
>>
>> Thanks for having a try, Mike. :) Actually the two context1 tasks
>> don't stack up on one logical cpu at the most of time which is
>> observed by kernelshark. Do you have any idea why there is 4.5 times
>> RESCHED IPIs which is mentioned in another reply for this thread?
>
> See resched_curr().
Yeah, I observe writer/reader pair is running on the same core
sometimes after more digging. Thanks Mike!
Regards,
Wanpeng Li
Powered by blists - more mailing lists