From: Jiri Olsa <jolsa@redhat.com>
To: "Wangnan (F)" <wangnan0@huawei.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
jolsa@kernel.org, namhyung@kernel.or, lizefan@huawei.com,
pi3orama@163.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] perf tools: Improve 'make build-test'
Date: Mon, 11 Jan 2016 09:46:08 +0100 [thread overview]
Message-ID: <20160111084608.GA15415@krava.brq.redhat.com> (raw)
In-Reply-To: <569319B6.1050901@huawei.com>
On Mon, Jan 11, 2016 at 10:55:50AM +0800, Wangnan (F) wrote:
> Hi Jiri,
>
> I think if we can fold the feature checking in build-test then
> it can be even faster. We need only 2 feature check result (for
> normal building and static building), but in a full build-test
> we run 138 rounds feature checking. Would you please give some
> help on it?
I think we can add separate target that will skip the feature
detection, given that there's extra call before generating
FEATURE-DUMP file.. I'll check on this
>
> Now I have a 160 cores server for building perf, currently busy
> time and idle time are 5:3 (result from top. I use 1s interval.
> Each test case takes about 8s, in about 5 seconds I can see
> full of 'cc1' in perf top result). A full test-build still require
> more than 0.3 hours (8s * 34 cases * 2 (with and without O) *
> 2 (Makefile and Makefile.perf) = 1088 seconds).
nice
thanks,
jirka
prev parent reply other threads:[~2016-01-11 8:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 14:23 [PATCH 0/6] perf tools: Improve 'make build-test' Wang Nan
2016-01-08 14:23 ` [PATCH 1/6] perf tools: Add -lutil in python lib list for broken python-config Wang Nan
2016-01-11 9:28 ` Jiri Olsa
2016-01-11 9:44 ` Wangnan (F)
2016-01-11 9:50 ` Wangnan (F)
2016-01-12 9:41 ` Jiri Olsa
2016-01-08 14:23 ` [PATCH 2/6] perf tools: Add missing headers in perf's MANIFEST Wang Nan
2016-01-09 16:37 ` [tip:perf/core] perf tools: Add missing headers in perf' s MANIFEST tip-bot for Wang Nan
2016-01-11 9:43 ` [PATCH] perf tools: Add missing sources in perf's MANIFEST Jiri Olsa
2016-01-11 9:46 ` Wangnan (F)
2016-01-11 14:12 ` Arnaldo Carvalho de Melo
2016-01-08 14:23 ` [PATCH 3/6] perf tools: Fix phony build target for build-test Wang Nan
2016-01-11 9:29 ` Jiri Olsa
2016-01-08 14:23 ` [PATCH 4/6] perf tools: Set parallel making options build-test Wang Nan
2016-01-11 9:38 ` Jiri Olsa
2016-01-08 14:24 ` [PATCH 5/6] perf tools: Pass O option to Makefile.perf in build-test Wang Nan
2016-01-08 14:24 ` [PATCH 6/6] perf tools: Test correct path of perf " Wang Nan
2016-01-08 14:32 ` [PATCH 0/6] perf tools: Improve 'make build-test' Arnaldo Carvalho de Melo
2016-01-11 2:55 ` Wangnan (F)
2016-01-11 8:46 ` Jiri Olsa [this message]
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=20160111084608.GA15415@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=namhyung@kernel.or \
--cc=pi3orama@163.com \
--cc=wangnan0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.