public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Barry Song <song.bao.hua@hisilicon.com>,
	valentin.schneider@arm.com, vincent.guittot@linaro.org,
	mgorman@suse.de, mingo@kernel.org, peterz@infradead.org,
	dietmar.eggemann@arm.com, morten.rasmussen@arm.com,
	linux-kernel@vger.kernel.org
Cc: linuxarm@openeuler.org, xuwei5@huawei.com,
	liguozhu@hisilicon.com, tiantao6@hisilicon.com,
	wanghuiqiang@huawei.com, prime.zeng@hisilicon.com,
	jonathan.cameron@huawei.com, guodong.xu@linaro.org
Subject: Re: [PATCH v3] sched/topology: fix the issue groups don't span domain->span for NUMA diameter > 2
Date: Tue, 9 Feb 2021 14:40:05 +0200	[thread overview]
Message-ID: <d091f321-540c-acc7-4340-72b80cbe7296@linux.ee> (raw)
In-Reply-To: <20210209082125.22176-1-song.bao.hua@hisilicon.com>

I did a rudimentary benchmark on the same 8-node Sun Fire X4600-M2, on top of todays  5.11.0-rc7-00002-ge0756cfc7d7c.

The test: building clean kernel with make -j64 after make clean and drop_caches.

While running clean kernel / 3 tries):

real    2m38.574s
user    46m18.387s
sys     6m8.724s

real    2m37.647s
user    46m34.171s
sys     6m11.993s

real    2m37.832s
user    46m34.910s
sys     6m12.013s


While running patched kernel:

real    2m40.072s
user    46m22.610s
sys     6m6.658s


for real time, seems to be 1.5s-2s slower out of 160s (noise?) User and system time are slightly less, on the other hand, so seems good to me.

-- 
Meelis Roos <mroos@linux.ee>

  parent reply	other threads:[~2021-02-09 12:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09  8:21 [PATCH v3] sched/topology: fix the issue groups don't span domain->span for NUMA diameter > 2 Barry Song
2021-02-09  9:46 ` Vincent Guittot
2021-02-09 11:46   ` Valentin Schneider
2021-02-09 13:10     ` Vincent Guittot
2021-02-09 11:28 ` Valentin Schneider
2021-02-09 12:40 ` Meelis Roos [this message]
2021-02-10  9:35   ` Song Bao Hua (Barry Song)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d091f321-540c-acc7-4340-72b80cbe7296@linux.ee \
    --to=mroos@linux.ee \
    --cc=dietmar.eggemann@arm.com \
    --cc=guodong.xu@linaro.org \
    --cc=jonathan.cameron@huawei.com \
    --cc=liguozhu@hisilicon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@openeuler.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=morten.rasmussen@arm.com \
    --cc=peterz@infradead.org \
    --cc=prime.zeng@hisilicon.com \
    --cc=song.bao.hua@hisilicon.com \
    --cc=tiantao6@hisilicon.com \
    --cc=valentin.schneider@arm.com \
    --cc=vincent.guittot@linaro.org \
    --cc=wanghuiqiang@huawei.com \
    --cc=xuwei5@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox