[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgpmV2B=s2xE5385Jzy2tEZuiW+MSPveJBfpqUoFdGydg@mail.gmail.com>
Date: Fri, 23 Nov 2018 10:44:22 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andy Lutomirski <luto@...capital.net>
Cc: David.Laight@...lab.com, Andrew Lutomirski <luto@...nel.org>,
dvlasenk@...hat.com, Jens Axboe <axboe@...nel.dk>,
Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, bp@...en8.de,
Peter Anvin <hpa@...or.com>,
"the arch/x86 maintainers" <x86@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>, brgerst@...il.com,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
pabeni@...hat.com
Subject: Re: [PATCH] x86: only use ERMS for user copies for larger sizes
On Fri, Nov 23, 2018 at 10:39 AM Andy Lutomirski <luto@...capital.net> wrote:
>
> What is memcpy_to_io even supposed to do? I’m guessing it’s defined as something like “copy this data to IO space using at most long-sized writes, all aligned, and writing each byte exactly once, in order.” That sounds... dubiously useful.
We've got hundreds of users of it, so it's fairly common..
> I could see a function that writes to aligned memory in specified-sized chunks.
We have that. It's called "__iowrite{32,64}_copy()". It has very few users.
Linus
Powered by blists - more mailing lists