From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S932507AbeAXIIA (ORCPT <rfc822;w@1wt.eu>);
        Wed, 24 Jan 2018 03:08:00 -0500
Received: from mail-ot0-f180.google.com ([74.125.82.180]:38570 "EHLO
        mail-ot0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932085AbeAXIH6 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 24 Jan 2018 03:07:58 -0500
X-Google-Smtp-Source: AH8x226p49G3kdIQhEJYTafi6U9kFNMKC9qNOm/RMLAtpWnv8L4Hv9pUKLLuhqdmDtVdFPLr25SuBkSp+4ZBIaQvQXE=
MIME-Version: 1.0
In-Reply-To: <1516715358.8747.27.camel@gmx.de>
References: <CANRm+CwpGoSTLNG3D8KN+fgfc+20-gFND7xGAYo2b5EuwzPeOg@mail.gmail.com>
 <1516622939.24679.5.camel@gmx.de> <CANRm+CyXVkQKbHFMQG4v3fjUuPOHpY15_c6gU+gaUzf_67xnFg@mail.gmail.com>
 <1516628254.7500.19.camel@gmx.de> <CANRm+CxpP-MNLsJS+-bu19Avp96=8jXrc4et1HE+-7SbKgGbPQ@mail.gmail.com>
 <1516715358.8747.27.camel@gmx.de>
From: Wanpeng Li <kernellwp@gmail.com>
Date: Wed, 24 Jan 2018 16:07:57 +0800
Message-ID: <CANRm+Cw7tg1=2CFua8-FOuJGPXdkRbgNNBOtGSoz1iJWuxXK2g@mail.gmail.com>
Subject: Re: unixbench context switch perfomance & cpu topology
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel@vger.kernel.org, kvm <kvm@vger.kernel.org>,
        Paolo Bonzini <pbonzini@redhat.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Radim Krcmar <rkrcmar@redhat.com>,
        Frederic Weisbecker <fweisbec@gmail.com>,
        Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

2018-01-23 21:49 GMT+08:00 Mike Galbraith <efault@gmx.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