[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170112185825.GE5020@rric.localdomain>
Date: Thu, 12 Jan 2017 19:58:25 +0100
From: Robert Richter <robert.richter@...ium.com>
To: Will Deacon <will.deacon@....com>
CC: Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Hanjun Guo <hanjun.guo@...aro.org>,
Russell King <linux@...linux.org.uk>,
Catalin Marinas <catalin.marinas@....com>,
David Daney <david.daney@...ium.com>,
Mark Rutland <mark.rutland@....com>,
James Morse <james.morse@....com>,
Yisheng Xie <xieyisheng1@...wei.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH v3] arm64: mm: Fix NOMAP page initialization
On 12.01.17 16:05:36, Will Deacon wrote:
> On Mon, Jan 09, 2017 at 12:53:20PM +0100, Robert Richter wrote:
> > Kernel compile times (3 runs each):
> >
> > pfn_valid_within():
> >
> > real 6m4.088s
> > user 372m57.607s
> > sys 16m55.158s
> >
> > real 6m1.532s
> > user 372m48.453s
> > sys 16m50.370s
> >
> > real 6m4.061s
> > user 373m18.753s
> > sys 16m57.027s
>
> Did you reboot the machine between each build here, or only when changing
> kernel? If the latter, do you see variations in kernel build time by simply
> rebooting the same Image?
I built it in a loop on the shell, so no reboots between builds. Note
that I was building the kernel in /dev/shm to not access harddisks. I
think build times should be comparable then since there is no fs
caching.
-Robert
Powered by blists - more mailing lists