From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17780 invoked by alias); 3 Sep 2013 16:18:34 -0000 Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-ports-owner@sourceware.org Received: (qmail 17768 invoked by uid 89); 3 Sep 2013 16:18:34 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 03 Sep 2013 16:18:34 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r83GIPoK022336 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 3 Sep 2013 12:18:25 -0400 Received: from [10.3.113.109] (ovpn-113-109.phx2.redhat.com [10.3.113.109]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id r83GIOAZ020874; Tue, 3 Sep 2013 12:18:24 -0400 Message-ID: <52260BD0.6090805@redhat.com> Date: Tue, 03 Sep 2013 16:18:00 -0000 From: "Carlos O'Donell" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130805 Thunderbird/17.0.8 MIME-Version: 1.0 To: Will Newton CC: "libc-ports@sourceware.org" , Patch Tracking , =?UTF-8?B?T25kxZllaiBCw61sa2E=?= , Siddhesh Poyarekar Subject: Re: [PATCH] sysdeps/arm/armv7/multiarch/memcpy_impl.S: Improve performance. References: <520894D5.7060207@linaro.org> <5220D30B.9080306@redhat.com> <5220F1F0.80501@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2013-09/txt/msg00019.txt.bz2 On 09/02/2013 09:58 AM, Will Newton wrote: >> If it's not obvious how is someone supposed to review this patch? :-) > > With difficulty. ;-) Thank you for acknowledging that. > Joseph has raised some good points about the comments and I'll go back > through the code and make sure everything is correct in that regard. > The change was actually made to the copy of the code in cortex-strings > some time ago but I delayed pushing the patch due to the 2.18 release > so I have to refresh my memory somewhat. > > Ideally we would have an agreed upon benchmark with which everyone > could analyse the performance of the code on their systems, however > that does not seem to exist as far as I can tell. We have one, it's the glibc microbenchmark, and we want to expand it, otherwise when ACME comes with their patch for ARM and breaks performance for targets that Linaro cares about I have no way to reject the patch objectively :-) > The key advantage of the cortex-strings framework is that it allows > graphing the results of benchmarks. Often changes to string function > performance can only really be analysed graphically as otherwise you > end up with a huge soup of numbers, some going up, some going down and > it is very hard to separate the signal from the noise. I disagree strongly. You *must* come up with a measurable answer and looking at a graph is never a solution I'm going to accept. You need to statistically analyze the numbers, assign weights to ranges, and come up with some kind of number that evaluates the results based on *some* formula. That is the only way we are going to keep moving performance forward (against some kind of criteria). > The glibc benchmarks also have some other weaknesses that should > really be addressed, hopefully I'll have some time to write patches > for some of this work. Thank you very much. Cheers, Carlos.