From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-15?Q?Matthias_Wei=DFer?= Date: Wed, 26 Jan 2011 13:50:53 +0100 Subject: [U-Boot] [PATCH V2] arm: Use optimized memcpy and memset from linux In-Reply-To: <4D400E99.9000800@free.fr> References: <1295884607-9044-1-git-send-email-weisserm@arcor.de> <1296038757-11800-1-git-send-email-weisserm@arcor.de> <4D400E99.9000800@free.fr> Message-ID: <4D4018AD.7090001@arcor.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Am 26.01.2011 13:07, schrieb Albert ARIBAUD: >> --- > > IIRC, the '---' line separates patch commit message (above) from > freeform comments and history (below). Here, at least the version > history should move below the '---' line. Wolfgang asked me that I add the numbers to the commit message. For the changelog I will investigate the git commands on how to do that best without manually editing the patch file before git send-email them. >> +- CONFIG_USE_ARCH_MEMCPY >> + CONFIG_USE_ARCH_MEMSET >> + If these options are used a optimized version of memcpy/memset will >> + be used if available. These functions may be faster under some >> + conditions but may increase the binary size. >> + > > The name of the options is not self-explaining to me. If the difference > is "generic vs arch-optimal", then maybe CONFIG_USE_ARCH_OPTIMAL_MEMxxx > would be a better name? Wolfgang didn't object on these names. If we use the OPTIMAL form it is still not clear what optimal mean. There may be a size optimized version and a speed optimized version. So we would need CONFIG_USE_ARCH_SPEED_OPTIMAL_MEMxxx which I personally dislike a lot as it is quite long. I also think that if there is an architecture specific function that it should be clear that this is optimal in some way. Thanks for review Regards Matthias