From: bgat@billgatliff.com (Bill Gatliff)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: big performance waste in memcpy_{from,to}io
Date: Fri, 13 Nov 2009 08:00:27 -0600 [thread overview]
Message-ID: <4AFD667B.3020505@billgatliff.com> (raw)
In-Reply-To: <20091113122438.GB29008@n2100.arm.linux.org.uk>
Russell King - ARM Linux wrote:
> The problem is whether optimising it will end up breaking existing users.
>
I say we throw in the optimized version and enable it by default, along
with a Kconfig to defeat it upon user request at build time (or maybe a
module parameter). And then see who complains.
b.g.
--
Bill Gatliff
bgat at billgatliff.com
next prev parent reply other threads:[~2009-11-13 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 16:49 ARM: big performance waste in memcpy_{from,to}io Hubert Feurstein
2009-11-12 18:44 ` Alexander Clouter
2009-11-13 11:32 ` Hubert Feurstein
2009-11-13 12:24 ` Russell King - ARM Linux
2009-11-13 12:42 ` Andy Green
2009-11-13 14:00 ` Bill Gatliff [this message]
2009-11-16 14:57 ` [RFC PATCH] ARM: add (experimental) alternative memcpy_{from, to}io() and memset_io() Hubert Feurstein
2009-11-13 15:16 ` ARM: big performance waste in memcpy_{from,to}io Hubert Feurstein
2009-11-13 23:14 ` Ben Dooks
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=4AFD667B.3020505@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).