[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20171024110905.GA31064@arm.com>
Date: Tue, 24 Oct 2017 12:09:05 +0100
From: Will Deacon <will.deacon@....com>
To: Mark Salyzyn <salyzyn@...roid.com>
Cc: linux-kernel@...r.kernel.org, Kees Cook <keescook@...omium.org>,
Anton Vorontsov <anton@...msg.org>,
Tony Luck <tony.luck@...el.com>,
Catalin Marinas <catalin.marinas@....com>,
linux-arm-kernel@...ts.infradead.org,
Colin Cross <ccross@...roid.com>,
Mark Salyzyn <salyzyn@...gle.com>
Subject: Re: [PATCH v2] arm64: optimize __memcpy_fromio and __memcpy_toio
On Mon, Oct 23, 2017 at 09:25:35AM -0700, Mark Salyzyn wrote:
> __memcpy_fromio and __memcpy_toio functions do not deal well with
> harmonically unaligned addresses unless they can ultimately be
> copied as quads (u64) to and from the destination. Without a
> harmonically aligned relationship, they perform byte operations
> over the entire buffer.
>
> Dropped the fragment that tried to align on the normal memory,
> placing a priority on using quad alignment on the io-side.
>
> Removed the volatile on the source for __memcpy_toio as it is
> unnecessary.
>
> This change was motivated by performance issues in the pstore driver.
> On a test platform, measuring probe time for pstore, console buffer
> size of 1/4MB and pmsg of 1/2MB, was in the 90-107ms region. Change
> managed to reduce it to 10-25ms, an improvement in boot time.
>
> Signed-off-by: Mark Salyzyn <salyzyn@...roid.com>
> Cc: Kees Cook <keescook@...omium.org>
> Cc: Anton Vorontsov <anton@...msg.org>
> Cc: Tony Luck <tony.luck@...el.com>
> Cc: Catalin Marinas <catalin.marinas@....com>
> Cc: Will Deacon <will.deacon@....com>
> Cc: Anton Vorontsov <anton@...msg.org>
> Cc: linux-arm-kernel@...ts.infradead.org
> Cc: linux-kernel@...r.kernel.org
>
> v2:
> - simplify, do not try so hard, or through steps, to align on the
> normal memory side, as it was a diminishing return. Dealing with
> any pathological short cases was unnecessary since there does not
> appear to be any.
> - drop similar __memset_io changes completely.
I'm fine with the idea here, but can you leave the '8's alone and not
replace them with sizeof(u64) please? I don't think it helps anybody,
and we still use ++/-- for the u8 case.
Will
Powered by blists - more mailing lists