iozone: new package
PATCH 1/1 iozone: new package
--- package/Config.in | 1 + package/iozone/Config.in | 14 ++++++++++++++ package/iozone/iozone.mk | 43 +++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 58 insertions(+), 0 deletions(-) create mode 100644 package/iozone/Config.in create mode 100644 package/iozone/iozone.mk
package/Config.in +1 -0
@@ -22,6 +22,7 @@ source "package/cache-calibrator/Config.in" source "package/dhrystone/Config.in" source "package/dstat/Config.in" source "package/dmalloc/Config.in" +source "package/iozone/Config.in" source "package/kexec/Config.in" source "package/latencytop/Config.in" source "package/lmbench/Config.in"
package/iozone/Config.in new file +14 -0
@@ -0,0 +1,14 @@ +config BR2_PACKAGE_IOZONE + bool "IOzone" + depends on BR2_TOOLCHAIN_HAS_THREADS + depends on BR2_LARGEFILE + depends on BR2_USE_MMU # fork() + help + IOzone is a filesystem benchmark tool. + The benchmark generates and measures a variety of file operations + + http://www.iozone.org/ + +comment "IOzone requires a toolchain with LARGEFILE and threads support" + depends on !(BR2_LARGEFILE && BR2_TOOLCHAIN_HAS_THREADS) +
package/iozone/iozone.mk new file +43 -0
43 lines not on this page · raw message
Signature · 1 line
1.7.4.1
PATCH 1/1 iozone: new package
Dear Gilles Talis,
package/iozone/iozone.mk line 9
Quoted 3 lines · Gilles Talis
package/iozone/iozone.mk new file +3
-0+IOZONE_MAJOR_VERSION = 3 +IOZONE_MINOR_VERSION = 414 +IOZONE_VERSION = $(IOZONE_MAJOR_VERSION)_$(IOZONE_MINOR_VERSION)
Any reason to split major and minor versions here? I only see IOZONE_VERSION used below.
package/iozone/iozone.mk line 21
Quoted 11 lines
package/iozone/iozone.mk new file +11
-0+IOZONE_SOURCE = iozone$(IOZONE_VERSION).tar +IOZONE_SITE = http://www.iozone.org/src/current +IOZONE_LICENSE = IOzone license (NO DERIVED WORKS ALLOWED) +# IOzone license details can be found at: +# http://www.iozone.org/docs/Iozone_License.txt + + +ifeq ($(BR2_arm)$(BR2_armeb),y) +IOZONE_TARGET = linux-arm +else ifeq ($(BR2_x86_64),y) +IOZONE_TARGET = linux-ia64
This seems wrong IA64 is the Itanium architecture from Intel, and not the x86-64 architecture.
package/iozone/iozone.mk line 28
Quoted 7 lines
package/iozone/iozone.mk new file +7
-0+else ifeq ($(BR2_powerpc),y) +IOZONE_TARGET = linux-powerpc +else ifeq ($(BR2_sparc),y) +IOZONE_TARGET = linux-sparc +else +IOZONE_TARGET = linux +endif
What happens for other architectures? Does it still build? What are the differences between those per-architecture make targets?
Thanks,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH 1/1 iozone: new package
Dear Thomas,
Quoted 4 lines
Quoted 1 line
+IOZONE_VERSION = $(IOZONE_MAJOR_VERSION)_$(IOZONE_MINOR_VERSION)
Any reason to split major and minor versions here? I only see
IOZONE_VERSIONused below.
No reason. I just felt it looked neater. But you're right, I'll just use IOZONE_VERSION.
Quoted 5 lines
package/iozone/iozone.mk line 21
Quoted 2 lines
package/iozone/iozone.mk new file +2
-0+else ifeq ($(BR2_x86_64),y) +IOZONE_TARGET = linux-ia64This seems wrong IA64 is the Itanium architecture from Intel, and not the x86-64 architecture.
Alright. I think I have to do some homework here.
Quoted 10 lines
package/iozone/iozone.mk line 28
Quoted 7 lines
package/iozone/iozone.mk new file +7
-0+else ifeq ($(BR2_powerpc),y) +IOZONE_TARGET = linux-powerpc +else ifeq ($(BR2_sparc),y) +IOZONE_TARGET = linux-sparc +else +IOZONE_TARGET = linux +endifWhat happens for other architectures? Does it still build? What are the differences between those per-architecture make targets?
Funnily enough, the only other targets I tested were i386 and PPC64 and it could build (target = linux)
Now, it fails to build for AVR32 and MIPS, as it can't find the async IO header file from uClibc.
IOzone can be built without aio though, using a "generic" target. Will see how to add this one in.
Also to answer your other question, the differences lie around file operations flags and functions (e.g usage of O_DIRECT or pread()).
Thanks
Gilles.