Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp3238884pxa; Tue, 18 Aug 2020 09:58:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx45AD9wiT9TY3cjNtjjm1sh04MH+gIlTpY1oU03r+INX2Po/6O+DPp/ZD8L9F7XAd2ZPpG X-Received: by 2002:a17:906:f1da:: with SMTP id gx26mr206606ejb.129.1597769887933; Tue, 18 Aug 2020 09:58:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597769887; cv=none; d=google.com; s=arc-20160816; b=GWRVq6JOIuhV/gIA4v2Xm1ZLZz9DBssr9RVavzy/yhcg2FbHNsDYpvZ/06VuVVxMp4 wTfQ9j7r6GVfk8cvDs3qQaSjD5oTt8J89dXBezDWFeHqPw00QgduWQjwQjZQdoMOF2bM 8dJfyOWL7h3Wsj/cBch8wE3QW2KLFp9D09Ly8cSbo+/4hBhUcU6TVheamJcJrd1/AUfi jPBHYq7pUa1oigVXwPy4ZEj3vnKzhMHfpY4OysfFtJNVi/x/Bho2eNztCafhdCq8ki/s UcNqkT5IP3rK1dhoKtf7YhTjA4rCQzQpfu4PacvckB5NkwaH2SxLorJjxNTx4Rcyo23n 1XvA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=lPIWo2NeK+L4V9brwkJLRapLBnNyx/xaLX/K9uVYdxM=; b=VMlx/OS/xyOUh1dzu+pVLVsdcJM958tP2Li/YgZONOX0pEJiiYwCcKZqz9+XdfdtqI sDTOW5OUB8lehYoE6zbuOMfEm9R6kGSUu+lo2kgtUQoK9gL83gPHpEnYb67+j6FDqf6q 2uhWfZRM0WcynR7YxucO1M7DUadxncAHr+Yi00J9o+DlZRlEASZDsDemKHMMX+D78IqV U9NmviwLmbKyA87QcXCpT88hWo9GRsuEcG66k9AlddjPft67JLO6+3OZz4nDmWNG6xwV a5rYGSgVf0rvRlHv5q6FEfPzYDrs4TaHeADWFNi/yt5ctXUEyGLFBx59crql3R6sH9Mp 4LvQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=ZgECNCAk; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z24si13314341ejr.308.2020.08.18.09.57.43; Tue, 18 Aug 2020 09:58:07 -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=@gmail.com header.s=20161025 header.b=ZgECNCAk; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728398AbgHRQyp (ORCPT + 99 others); Tue, 18 Aug 2020 12:54:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46642 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728341AbgHRQy1 (ORCPT ); Tue, 18 Aug 2020 12:54:27 -0400 Received: from mail-lj1-x241.google.com (mail-lj1-x241.google.com [IPv6:2a00:1450:4864:20::241]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A33E4C061389; Tue, 18 Aug 2020 09:54:26 -0700 (PDT) Received: by mail-lj1-x241.google.com with SMTP id w25so22177558ljo.12; Tue, 18 Aug 2020 09:54:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=lPIWo2NeK+L4V9brwkJLRapLBnNyx/xaLX/K9uVYdxM=; b=ZgECNCAkk3B8lk/fAw6iMFOE5H2BR46xjKJiQMeVnkHyBmCjVTOxb0EcXLXkNeUdug 8cTDLECRzSlrI8fTgbzE3Ci9uQTraDnEyYW77n+T91YPO5SeIrVu4JEo7BxSU/plqPHO 9Dr/ozz2Yn4F8OOLGx0mb42pn3+Gs0XrS9y+ohg3837XcZjIQLBXZZPjUVb2+wipujEW MJ+mcOOZXj6yktTuddx7IJJN5xxDRQ7x1cSBsLyyO2IM+iqxlKlNLn8G7oFqeaTDVU/e gc2mZvDZ6SDKui20rZ0SWN5CLw7ADal3/+IgF2MfUz97KEFl/3m3chSew8pb+n2+Vh70 zHWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=lPIWo2NeK+L4V9brwkJLRapLBnNyx/xaLX/K9uVYdxM=; b=Do4SW2tPw8xM2Udc7yjvav7dgG03pShjC5PlHE42qS5jRBcFlPaFDm8SxA1nL5b0au /lm+B3W6PDCvBlrfSdWGwF+Q0ilIa6jtfcarhJodfXXmYEAgM0fX9P8ckjy8F9nkjITO TCLJPxovTpisTN4EJpZKsq2PIbBKUWJ9AA4K1QfuUoEJqjeS6goKunZlpPqxO3jcvh2L 38InVOleEc+WlLDjUM9DTTAEoOmadU63tXZi8Kyb/DEpZo1M+vrMxiSa5LX0lozotUcE Pec5FtiUmhAtuh57gcLYFuJvJ+7pZr7cggUDAn1+CzbXl4uQTX0bi3KQN546cvixgz2x d99g== X-Gm-Message-State: AOAM532MN5zljtLHFA1eUAutSRnLnn7kBfJS+XPmFwtwccRtsdmCjQ5B yiLt6RJdyTNk5pwkWaN0UFy5YzRK+L07vAzPjeY= X-Received: by 2002:a2e:1418:: with SMTP id u24mr9850592ljd.120.1597769665005; Tue, 18 Aug 2020 09:54:25 -0700 (PDT) MIME-Version: 1.0 References: <20200818143633.GA628293@kroah.com> In-Reply-To: <20200818143633.GA628293@kroah.com> From: Muni Sekhar Date: Tue, 18 Aug 2020 22:24:13 +0530 Message-ID: Subject: Re: Scheduler benchmarks To: Greg KH Cc: kernelnewbies , linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 8:06 PM Greg KH wrote: > > On Tue, Aug 18, 2020 at 08:00:11PM +0530, Muni Sekhar wrote: > > Hi all, > > > > I=E2=80=99ve 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) benchmar= k result: > > > > $ perf bench sched messaging -g 64 > > # Running 'sched/messaging' benchmark: > > # 20 sender and receiver processes per group > > # 64 groups =3D=3D 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 =3D=3D 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 :) I created the difference between two kernel config files and then tried to spot the CONFIG*SCHED* differences. Interestingly I see the difference in I/O scheduler config, 1st system is set to =E2=80=9Cdeadline=E2=80=9D and other one is set to =E2=80=9Ccfq= =E2=80=9D. So I made it equal by echoing to =E2=80=9C/sys/block//queue/scheduler" but still = no change in scheduler benchmark metrics. Is it the correct way to find the differences between kernels? If so, what other important CONFIG_* variables need to consider? $ cat config.patch | grep -i sched CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=3Dy CONFIG_CGROUP_SCHED=3Dy CONFIG_FAIR_GROUP_SCHED=3Dy # CONFIG_RT_GROUP_SCHED is not set # IO Schedulers @@ -369,10 +434,14 @@ CONFIG_IOSCHED_NOOP=3Dy CONFIG_IOSCHED_DEADLINE=3Dy CONFIG_IOSCHED_CFQ=3Dy CONFIG_CFQ_GROUP_IOSCHED=3Dy -CONFIG_DEFAULT_IOSCHED=3D"deadline" +CONFIG_DEFAULT_IOSCHED=3D"cfq" +CONFIG_MQ_IOSCHED_DEADLINE=3Dm +CONFIG_MQ_IOSCHED_KYBER=3Dm +CONFIG_IOSCHED_BFQ=3Dm +CONFIG_BFQ_GROUP_IOSCHED=3Dy CONFIG_SCHED_SMT=3Dy CONFIG_SCHED_MC=3Dy +CONFIG_SCHED_MC_PRIO=3Dy +# CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set +CONFIG_CPU_FREQ_GOV_SCHEDUTIL=3Dy > > good luck! > > greg k-h --=20 Thanks, Sekhar