Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp3141944pxa; Tue, 18 Aug 2020 07:40:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxFrdckPhATDl6GQxmS+7y7jDM7sA3IHyj4N9MS/B1fm0sWaMA3Xbti4191MxRQMIuhJTKG X-Received: by 2002:a05:6402:1218:: with SMTP id c24mr19609888edw.44.1597761628253; Tue, 18 Aug 2020 07:40:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597761628; cv=none; d=google.com; s=arc-20160816; b=v/bNEwaKSi7eaDesAhKYzIAqKcMPp6NOiAsrbXjXCFcdDDJryORGSTb4Tt01/ReOrp ipMRuyIcfpDscseZooHfPgNJZY2jPu/uF1zurTmuqu2jw9aM0TpNKcxxGbeJ7IRJ08Qj K4vS7qByrlFdQDQTfDaUFHzVu+zTh8zoyGSfH+3rTWyCz/gNZxO1jEUg8f/fTdKXID6B FH8HVC2NHZJaBYRCN2GiM6j7Gea/drHfk6PGIZ0I/+OqsXJqUoIiDwVsg7TMiNfiqltS HkmfihAgAw9SWlZTRssdxnlwBx3StziyXVEzofUBTn1LiAlxg7u8lfJuX0YsnZ18Z8sZ 3mkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:dkim-signature; bh=5TdnmIs67JzoUO77MgRwZ9vTwpz13W5GGUJXcewViJs=; b=jMkJfVqMmLOpXvOvSOGLWdKHAW5NGuO39yuFXQ766PfRfQHiZrliORIbGAllDsmN6l QJSLJGherIYYWI/t8/iJ+F0GT7ywXtCYh+T/wVl97gD8afCt3z1QvTBXocJlQJHVIWuP Wydd9LTy5GUtapGjd+dGJLPWW8hfqIcNiBvci+wH5rnhcXRDpaxhB8U7hpo2StNsKQRF JUVT37LQrrYs2XnFoMjM3kL0WLrPmij40J5a39V5x4HbAoQ4NxpsEYgx+ouwEVh+aKhu mJX9063P4NJyLDyBq4Yl8GStVzRZNHT69waH1y0+BR9HAN1i5d0NHl712508e3xndvoC KWpQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm1 header.b=HPhBTxMU; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=uPmw7Isx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u22si13002492edy.546.2020.08.18.07.40.03; Tue, 18 Aug 2020 07:40:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kroah.com header.s=fm1 header.b=HPhBTxMU; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=uPmw7Isx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727846AbgHROgN (ORCPT + 99 others); Tue, 18 Aug 2020 10:36:13 -0400 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]:38043 "EHLO wout3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727782AbgHROgM (ORCPT ); Tue, 18 Aug 2020 10:36:12 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 52DCFFC5; Tue, 18 Aug 2020 10:36:11 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 18 Aug 2020 10:36:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:content-transfer-encoding:in-reply-to; s=fm1; bh=5 TdnmIs67JzoUO77MgRwZ9vTwpz13W5GGUJXcewViJs=; b=HPhBTxMUoeE0g+wHy i7VlPgVyLeE/N5FhgpYbqOwJ4oYtmowcOpiSg0m9MsJ95x9rR0MMF2DxOkYMa131 VjI8alZNnJ2wej6wpaRv3fc0NpmZEi1Zl0OkZ8O0ZNuW0CDcLret5QTCmisoMWb9 hF8ouE+xk3/nYo7x6iMm2bGtUNoKrvbOnJw47Ji3DMDWS4lOGtoVGIzCyBQdjm5l yorOwUKDqsTNJXt1ak+UTht9KcwaT902rD0nLIpVqW2AVRCgxElG1BkXlU4JhkT4 J2pPwvPoFRcjQlhRvmmDinRkOWlW4m3a9DAtXWv9TKu9TfLKjoXcKEDbApNRlgft UcxRw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=5TdnmIs67JzoUO77MgRwZ9vTwpz13W5GGUJXcewVi Js=; b=uPmw7IsxLGcFxk4Mh9WKHeImfCPK2ESrm9PrjLoivh6pf7OXTNhwHVjsb PNCVdH40asSmnoOTphbxZhdXodBw4/1D0Nj4uJytd5ZNYxJamNfnqDW3AkyLfxpf fy8v4cl2ey/znQswsE42CBWn0rY5XpL3akodsUizEJfmgdwjyOOdITx4CjhS63SU l/LJmphBY+H9jIWQvNM/StW+TDvSJQitdcvesHkzCM9ycctsZ95BX+A+2ABxwGbk FSTWbJSXkhXWN7eL1gsT5moANMcwByLkBmfzBPqERY/WyRCX1VTwbiUkP+ejezXa mkZbV/khhKstf6XMdnMKGobeM3Jng== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedruddtiedgieejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggugfgjsehtke ertddttdejnecuhfhrohhmpefirhgvghcumffjuceoghhrvghgsehkrhhorghhrdgtohhm qeenucggtffrrghtthgvrhhnpeeuheekheelffefieduteefkeejffdvueehjeejffehle dugfetkedvleekudduvdenucfkphepkeefrdekiedrkeelrddutdejnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrd gtohhm X-ME-Proxy: Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id 46AA9328005D; Tue, 18 Aug 2020 10:36:10 -0400 (EDT) Date: Tue, 18 Aug 2020 16:36:33 +0200 From: Greg KH To: Muni Sekhar Cc: kernelnewbies , linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org Subject: Re: Scheduler benchmarks Message-ID: <20200818143633.GA628293@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 18, 2020 at 08:00:11PM +0530, Muni Sekhar wrote: > Hi all, > > I’ve two identical Linux systems with only kernel differences. What are the differences in the kernels? > While doing kernel profiling with perf, I got the below mentioned > metrics for Scheduler benchmarks. > > 1st system (older kernel version compared to the other system) benchmark result: > > $ perf bench sched messaging -g 64 > # Running 'sched/messaging' benchmark: > # 20 sender and receiver processes per group > # 64 groups == 2560 processes run > > Total time: 2.936 [sec] > > > 2nd system benchmark result: > > $ perf bench sched messaging -g 64 > # Running 'sched/messaging' benchmark: > # 20 sender and receiver processes per group > # 64 groups == 2560 processes run > > Total time: 10.074 [sec] > > > So as per scheduler benchmark results, clearly a huge difference > between two systems. > Can anyone suggest to me how to dive deeper to know the root cause for > it. Look a the differences between your different kernels, that would be a great start :) good luck! greg k-h