'''What the project is all about''' Currently, Fedora only supports armv5tel codes. With the release of armv7 architecture (with beagleboardXM) Fedora-ARM is pressed with the decision of upgrading its Fedora Universe to use armv7 code. While it seems logical, re-compiling the whole Fedora package is a strenuous task. Before deciding to recompile the whole universe, Fedora-Run ARM can test if optimizing certain system binaries to use armv7 architecture provides significant performance difference against the currently used armv5tel codes. The test would clarify if armv7 codes used for armv7 hardware really improves system performance. This project aims for that sole purpose. By running a benchmark and compiler optimizations on armv5tel system binaries, Fedora-ARM can contrast both technologies and armv7tel use the results to decide if it's really worth to recompile the whole Fedora Universe to use armv7 codes. Below is a list of technologies by armv7. '''ARMv7''' Technologies:<ul> <li>[http://www.arm.com/about/newsroom/319.php Thumb®-2/ Thumb]</li> <li>[http://www.arm.com/products/processors/technologies/neon.php NEON™]</li> <li>[http://www.arm.com/products/processors/technologies/vector-floating-point.php VFPv3]</li></ul>  There are currently 2 '''ARMv7''' (beagleboard & beagleboard XM) builders in the Fedora ARM farm. These builders are running builds on '''ARMv5tel'''. This project will focus in using the beagleboardXM builder <code>cdot-beagleXM-0-3</code> ===Specifications for the cdot-beagleboardXM-0-3 builder===----[[Image:Bb.jpg|thumb|right|400px| cdot-beagleboardXM-0-3 builder]]'''beagleboardXM specific'''<br /><blockquote>[http://beagleboard.org/hardware-xM beagleboardXM hardware page]</blockquote>'''cat /proc/version'''<blockquote>Linux version 2.6.32 (ubuntu@ip-10-204-115-71) (gcc version 4.3.3 (GCC) ) #3 PREEMPT Wed Aug 18 15:53:03 UTC 2010</blockquote>'''cat /proc/cpuinfo'''<blockquote>Processor : ARMv7 Processor rev 2 (v7l)<br />BogoMIPS : 515.72<br />Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3<br />CPU implementer : 0x41<br />CPU architecture: 7<br />CPU variant : 0x3<br />CPU part : 0xc08<br />CPU revision : 2<br />Hardware : OMAP3 Beagle Board<br />Revision : 0020<br />Serial : 0000000000000000<br /></blockquote>'''cat /proc/meminfo'''<br /><blockquote>MemTotal: 498716 kB</blockquote>

* ===[0.1] Optimize and run a benchmark program specifically designed to make use of <code>glibc</code>=== Any packages compiled for the beagleboards can be installed without optimization. So far, in the case of <code>cdot-beagleXM-0-3</code> packages are compiled without it. Without optimizations, software installed in a system can only run on sub-optimal performance. In order to make use of ARMv7 architecture features, editing the <code>CFLAGS</code> to use <code>arm</code> optimization options will let the compiler attempt to improve the performance and/or code size of the program; resulting in a more efficient/faster system. The goal of this release is to run a benchmark software named [http://en.wikipedia.org/wiki/Dhrystone Dhrystone] on <code>cdot-beagleXM-0-3</code> and record the results. Three (3) runs are required: '''No optimization''', '''Optimized for armv5tel''', and '''Optimized for armv7'''. Dhrystone is chosen as the benchmark software mainly, to test the general system performance of <code>cdot-beagleXM-0-3</code> and to test how much performance gain can be expected from optimizing a program. Other reasons include:<blockquote><b><font style="font-size:100%">Reasons for using Dhrystone</font></b>*ARM® recognizes the program and uses it as a performance attribute of their processors.*Dhrystone provides a more meaningful MIPS (Million Instructions Per Second) because results are compared to a reference machine.* Dhrystone numbers reflect the performance of the C compiler and libraries more so than the performance of the processor itself. (considered as a weakness of the program)*Check if armv7 optimization options and armv5tel optimization options differ significantly in program performance</blockquote>  [[Image:graph.png|thumb|450px|right| A graph showing the overall system performance of cdot-beagleXM-0-3]]  '''Test Result (in DMIPS):'''<br /> Normal = 758.869322709 DMIPS<br />Optimized for armv5tel = 1034.82179852 DMIPS<br />Optimized for armv7 = 1034.82179852 DMIPS<br />     The benchmark graph shows that optimization increased the overall performance of cdot-beagleXM-0-3 by '''36%''' (Normal run vs. Optimized for armv5tel/armv7). The results for both armv5tel and armv7 optimizations are the same. (It can be assumed that the armv5tel glibc impacts the performance of C library dependent programs such as Dhrystone). Another possible reason is that the compiler used is already armv7 optimized (since dhrystone also relies on the compiler efficiency) The data gathered can be used as a reference for conducting 0.2project release.<br /><br /><br />* <br /><br /><br /><br /><br /> ===[0.2] Install an armv7 glibc and re-run the benchmark using dhrystone=== Since optimizing the benchmark program using both architecture optimizations revealed the same results, optimizing the system binaries and re-running the benchmark should be able to provide a more concrete contrast between the 2 architectures. The goal of this release is to find out if upgrading the armv5tel glibc would affect the performance of a C library dependent program such as dhrystone. By re-installing glibc using armv7 optimizations and re-running an armv7 optimized dhrystone; a better benchmark result is expected (Higher DMIPS). The result would be beneficial for Fedora-ARM, for it will help the community decide if armv5tel codes should continually be supported.  '''Requires:''' <blockquote>[http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=8721 glibc binaries]</blockquote> In order for a successful glibc armv7 build, the file ''/usr/lib/rpm/redhat/rpmrc'' needs edit to use armv7 build options. Using mock; a downloaded glibc source can be rebuilt. Once finished, the binaries can then be installed locally to the system using rpm OR a local repository can be created enabling the use of yum.  '''Test Result:''' The Dhrystone (DMIPS) results never changed. The benchmark brought the same, exact number of DMIPS. Although Dhrystone does make use of C library functions and is assumed that the glibc would have effects on the program; the results proved that upgrading the glibc did not bring what's expected. It is proven that armv7 and armv5 arch optimizations provide the same level of performance especially when running C library dependent programs on cdot-beagleXM-0-3 builder. Why is it possible when armv7 architecture is supposed to be better than armv5tel? One big answer is that the system tested was built to use an [http://en.wikipedia.org/wiki/Application_binary_interface ABI] called "softfp". Although beagleboardXM (cortex-a8)supports the "hard floating-point" ABI, The Fedora-ARM currently can't afford to waste time building a system that supports "hardfp" solely on test purposes. To make things a little clearer, cdot-beagleXM-0-3 can't use the technology offered by ARM-cortex-a8 processor because of how the system (down to the lowest level) is built.  ARM Floating point is a pretty big topic, provided are some links to help you understand more. <ul><li>[http://en.wikipedia.org/wiki/IEEE_754-2008 Standard for floating point arithmetic]</li><li>[http://www.arm.com/products/processors/technologies/vector-floating-point.php ARM Floating Point]</li><li>[https://wiki.linaro.org/Linaro-arm-hardfloat arm-hardfloat wiki]</li><li>[http://gcc.gnu.org/wiki/Software_floating_point Software floating point in GCC]</li></ul> In conclusion, Fedora-ARM can continue to use armv5tel codes on armv7 machines. Deciding to recompile the whole universe for armv7 is somehow an inconvenient recommendation for now. ===[0.3] Future project prospect===The previous test didn't leave an opportunity for me to work on [0.3] Release. Although the comparison is done, and the results are gathered; One last option to test armv7 technology still remains: "Rebuild everything to use a hardfp ABI!" This recommendation would undoubtedly reveal the performance difference of armv7 against armv5tel; but at the same time would be a big project "not suitable for a single person to work on". I hope that this project page including the [http://zenit.senecac.on.ca/wiki/index.php/Dhrystone_howto Dhrystone How To] page can be of use for future ARM based project reference.

-Familiarization of the with ARM hardware<br /> === HOW TOs ===[http://zenit.senecac.on.ca/wiki/index.php/Dhrystone_howto A guide for using Dhrystone benchmark]

''December 16th, 2010'' - [0.2] and [0.3] Release updated and finalized ''December 15th, 2010'' - Added the [http://zenit.senecac.on.ca/wiki/index.php/Dhrystone_howto Dhrystone How to Page] ''December 9th, 2010'' - Project page update (0.1 Release) ''November 22nd, 2010'' - Release 0.1 test results posted ''November 4th, 2010'' - Compiler optimization options ready for testing, project page updated ''October 1519th, 2010'' - Chris Tyler explained more about the project, including goal 0.1  ''October 15th, 2010'' - Project page updated (Things to learn)