Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 13 Nov 2019 23:30:58 +0100 (CET)
From:   Thomas Gleixner <tglx@linutronix.de>
To:     Arnd Bergmann <arnd@arndb.de>
cc:     y2038@lists.linaro.org, Steven Rostedt <rostedt@goodmis.org>,
        Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org,
        Anna-Maria Gleixner <anna-maria@linutronix.de>,
        Frederic Weisbecker <frederic@kernel.org>,
        John Stultz <john.stultz@linaro.org>,
        Nicolas Pitre <nico@fluxnic.net>
Subject: Re: [PATCH 22/23] [RFC] y2038: itimer: use ktime_t internally
In-Reply-To: <20191108211323.1806194-13-arnd@arndb.de>
Message-ID: <alpine.DEB.2.21.1911132329330.2507@nanos.tec.linutronix.de>
References: <20191108210236.1296047-1-arnd@arndb.de> <20191108211323.1806194-13-arnd@arndb.de>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, 8 Nov 2019, Arnd Bergmann wrote:
> Avoid the intermediate step going from timeval to timespec64 to
> ktime_t and back by using ktime_t throughout the code.
> 
> I was going back and forth between the two implementations.
> This patch is optional: if we want it, it could be folded into
> the patch converting to itimerspec64.
> 
> On an arm32 build, this version actually produces 10% larger
> code than the timespec64 version, while on x86-64 it's the
> same as before, and the number of source lines stays the
> same as well.

Right. For 32bit without a native 64/32 division this is going to be more
text and I'm not really convinvced that this buys us anything.

Thanks,

	tglx