Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package iozone for openSUSE:Factory:NonFree 
checked in at 2021-01-25 18:20:58
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory:NonFree/iozone (Old)
 and      /work/SRC/openSUSE:Factory:NonFree/.iozone.new.28504 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "iozone"

Mon Jan 25 18:20:58 2021 rev:10 rq:864602 version:3.491

Changes:
--------
--- /work/SRC/openSUSE:Factory:NonFree/iozone/iozone.changes    2020-09-07 
21:20:07.140961040 +0200
+++ /work/SRC/openSUSE:Factory:NonFree/.iozone.new.28504/iozone.changes 
2021-01-25 18:20:59.164203275 +0100
@@ -1,0 +2,6 @@
+Wed Jan 20 09:26:32 UTC 2021 - Martin Pluskal <mplus...@suse.com>
+
+- Update to version 3_491:
+  * Fix CFLAGS issue from Fedora maintainer.
+
+-------------------------------------------------------------------

Old:
----
  iozone3_490.tar

New:
----
  iozone3_491.tar

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ iozone.spec ++++++
--- /var/tmp/diff_new_pack.wP2NaP/_old  2021-01-25 18:21:00.176204719 +0100
+++ /var/tmp/diff_new_pack.wP2NaP/_new  2021-01-25 18:21:00.180204725 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package iozone
 #
-# Copyright (c) 2020 SUSE LLC
+# Copyright (c) 2021 SUSE LLC
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -17,7 +17,7 @@
 
 
 %define src_version 3
-%define src_release 490
+%define src_release 491
 Name:           iozone
 Version:        %{src_version}.%{src_release}
 Release:        0
@@ -42,10 +42,10 @@
 This package contains the documentation for using and interpreting results of 
Iozone
 
 %prep
-%setup -q -n %{name}%{src_version}_%{src_release}
+%autosetup -n %{name}%{src_version}_%{src_release}
 
 %build
-%make_build CFLAGS="%{optflags} -DHAVE_PREADV -DHAVE_PWRITEV" -C src/current 
linux
+%make_build CFLAGS="%{optflags} -DHAVE_PREADV -DHAVE_PWRITEV -fPIE" -C 
src/current linux
 
 %install
 install -D -p -m 0755 src/current/iozone %{buildroot}%{_bindir}/iozone

++++++ iozone3_490.tar -> iozone3_491.tar ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/iozone3_490/docs/README new/iozone3_491/docs/README
--- old/iozone3_490/docs/README 2020-07-13 19:17:40.000000000 +0200
+++ new/iozone3_491/docs/README 1970-01-01 01:00:00.000000000 +0100
@@ -1,3 +0,0 @@
-Files in this directory are copied into web/docs. Be careful about
-using path relative links.
-
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/iozone3_490/docs/Template 
new/iozone3_491/docs/Template
--- old/iozone3_490/docs/Template       2020-07-13 19:17:40.000000000 +0200
+++ new/iozone3_491/docs/Template       1970-01-01 01:00:00.000000000 +0100
@@ -1,149 +0,0 @@
-#
-# This is the result template to be used for reporting Iozone runs.
-# The form is edited by the person doing the submission and 
-# is processed by a script on the web server. Please follow the
-# format described for each parameter.
-#
-#
-#
-# Number of cpus in the system = Integer in quotes.
-Number of cpus in the system =  "#"
-
-# Total amount of memory in the system = Integer in Megabytes in quotes.
-Total amount of memory in the system = "####"
-
-# Total amount of buffer cache in the system = Integer in Megabytes in quotes.
-Total amount of buffer cache in the system = "####"
-
-# Total number of disks in the system = Integer in quotes.
-Total number of disks in the system = "###"
-
-# Complete description of the layout of the disks in the system = ASCII text 
in quotes
-Disk layout = " "
-
-# Type of cpu = ASCII text in quotes
-Type of cpu = " "
-
-# Processor clock speed =  Integer in megahertz in quotes.
-Clock speed = "###"
-
-# Processor cache size = Integer in Kilobytes in quotes
-Processor cache size = "###"
-
-# External cache size = Integer in Kilo bytes in quotes.
-External cache size = "###"
-
-# Type of disk controllers = ASCII text in quotes
-Type of disk controllers = " "
-
-# Number of disk controllers = Integer in quotes
-Number of disk controllers = "###"
-
-# Type of disks = ASCII text in quotes
-Type of disks = " "
-
-# If using striping, include a complete description of the stripe layout
-Striping =  " "
-
-# Command line that was issued to Iozone  = ASCII text in quotes 
-Command used =  " "
-
-# Version number of Iozone used for the tests. = ASCII text in quotes.
-Version number of Iozone used for the tests = " "
-
-# Version of the Operating system = ASCII text in quotes.
-Version of the Operating system = " "
-
-# Availability dates of all software and hardware used. ASCII text in quotes.
-Availability dates of all software and hardware used = " "
-
-# Type of filesystem being used. = ASCII text in quotes.
-Type of filesystem being used = " "
-
-# Total amount of NVRAM in the system. (including the disks, disk controllers)
-# = Integer in kilobytes in quotes
-Total amount of NVRAM in the system = "###"
-
-# Date when tested  = ASCII text in quotes
-Date when tested = " "
-
-# Any other hardware used in the test. = ASCII text in quotes.
-Any other hardware used in the test = " "
-
-# Compiler options used to compile Iozone = ASCII text in quotes.
-Compiler options used to compile Iozone = " "
-
-# Options used to create the filesystems = ASCII text in quotes.
-Options used to create the filesystems = " "
-
-# Options used to mount the filesystems = ASCII text in quotes.
-Options used to mount the filesystems = " "
-
-# List of all tunables that were applied to the system = ASCII text in quotes.
-List of all tunables that were applied to the system = " "
-
-# Company name if publishing for a company = ASCII text in quotes.
-Company name if publishing for a company = " "
-
-# Name of the person that ran Iozone and their email address = ASCII text in 
qutoes
-Person that ran Iozone and their email address = " "
-
-#
-# NFS section. Only needed if the testing was over NFS.
-#
-#
-# Model of client = ASCII text in quotes.
-Model of client = " "
-
-# Client processor type = ASCII text in quotes.
-Client processor type = " "
-
-# Client processor clock speed = Integer in Megahertz in quotes
-Client processor clock speed = "###"
-
-# Client processor cache size = Integer in Kilobytes in quotes
-Client processor cache size = "###"
-
-# Client external cache size = Integer in Kilo bytes in quotes.
-Client external cache size = "###"
-
-# Client operating system version = ASCII text in quotes
-Client operating system version = " "
-
-# Availability dates of client = ASCII text in quotes
-Availability dates of client = " "
-
-# Version of NFS protocol used = "NFSV2" or "NFSV3"
-Version of NFS protocol used = 
-
-# Transport protocol used = "UDP" or "TCP"
-Transport protocol used =
-
-# Number of network controllers used = Integer in quotes
-Number of network controllers used = "#"
-
-# Type of network controllers used = ASCII text in quotes
-Type of network controllers used = ""
-
-# Type of network switches/hubs used = ASCII text in quotes
-Type of network switches/hubs used = ""
-
-# Client mount options used = ASCII text in quotes
-Client mount options used = " "
-
-#
-# Raw Iozone output file with the -R option enabled. ASCII text beginning with
-# RESULTS BEGIN and ending with RESULTS END text strings.
-Raw Iozone output  = 
-RESULTS BEGIN
-
-       Results go here.
-
-RESULTS END
-
-# Comments to help cover anything not covered in the above description.
-# Comments = ASCII text in quotes
-Comments = ""
-#
-#
-
Binary files old/iozone3_490/docs/badread.gif and 
new/iozone3_491/docs/badread.gif differ
Binary files old/iozone3_490/docs/read.gif and new/iozone3_491/docs/read.gif 
differ
Binary files old/iozone3_490/docs/read.jpg and new/iozone3_491/docs/read.jpg 
differ
Binary files old/iozone3_490/docs/read_latency.gif and 
new/iozone3_491/docs/read_latency.gif differ
Binary files old/iozone3_490/docs/read_latency.jpg and 
new/iozone3_491/docs/read_latency.jpg differ
Binary files old/iozone3_490/docs/read_scaling.gif and 
new/iozone3_491/docs/read_scaling.gif differ
Binary files old/iozone3_490/docs/read_scaling.jpg and 
new/iozone3_491/docs/read_scaling.jpg differ
Binary files old/iozone3_490/docs/reread.gif and 
new/iozone3_491/docs/reread.gif differ
Binary files old/iozone3_490/docs/reread_latency.gif and 
new/iozone3_491/docs/reread_latency.gif differ
Binary files old/iozone3_490/docs/reread_latency.jpg and 
new/iozone3_491/docs/reread_latency.jpg differ
Binary files old/iozone3_490/docs/rewrite.gif and 
new/iozone3_491/docs/rewrite.gif differ
Binary files old/iozone3_490/docs/rewrite_latency.gif and 
new/iozone3_491/docs/rewrite_latency.gif differ
Binary files old/iozone3_490/docs/write_latency.gif and 
new/iozone3_491/docs/write_latency.gif differ
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/iozone3_490/index.html new/iozone3_491/index.html
--- old/iozone3_490/index.html  2020-07-13 19:17:40.000000000 +0200
+++ new/iozone3_491/index.html  1970-01-01 01:00:00.000000000 +0100
@@ -1,77 +0,0 @@
-<HTML>
-<HEAD>
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
-<META NAME="Generator" CONTENT="Microsoft Word 97">
-<TITLE>Iozone Filesystem Benchmark</TITLE>
-<META NAME="keywords" CONTENT="Filesystem benchmark performance iozone disk 
IO">
-<META NAME="Template" CONTENT="C:\PROGRAM FILES\MICROSOFT 
OFFICE\OFFICE\html.dot">
-</HEAD>
-<BODY TEXT="#000000" LINK="#0000ff" VLINK="#808000" BGCOLOR="#ffffff">
-
-<P><HR></P>
-<H2 ALIGN="CENTER">IOzone Filesystem Benchmark</H2>
-<P><HR></P>
-<P><div align="center"></P>
-<P ALIGN="CENTER"><CENTER><TABLE CELLSPACING=0 BORDER=0 CELLPADDING=2 
WIDTH=800>
-<TR><TD WIDTH="50%" VALIGN="MIDDLE">
-<P><B>IOzone</B> is a filesystem benchmark tool. The benchmark generates and 
measures a variety of file operations. Iozone has been ported to many machines 
and runs under many operating systems. Iozone is useful for performing a broad 
filesystem analysis of a vendor?s computer platform. The benchmark tests file 
I/O performance for the following operations:</P><DIR>
-<DIR>
-
-<I><FONT SIZE=2><P>Read, write, re-read, re-write, read backwards, read 
strided,<BR>
-fread, fwrite, random read, pread ,mmap, aio_read, aio_write </DIR>
-</DIR>
-</I></FONT></TD>
-<TD WIDTH="50%" VALIGN="MIDDLE">
-<P><A HREF="docs/read.gif"><IMG SRC="docs/read.jpg" BORDER=0 WIDTH=400 
HEIGHT=296 ALT="The HFS Normal Read graph illustrates the single stream 
performance of reading files in various record"></A></TD>
-</TR>
-</TABLE>
-</CENTER></P>
-
-<P ALIGN="CENTER"></div><div align="center"></P>
-<P ALIGN="CENTER"><CENTER><TABLE CELLSPACING=0 BORDER=0 CELLPADDING=2 
WIDTH=800>
-<TR><TD WIDTH="50%" VALIGN="TOP">
-<P><A HREF="docs/read_scaling.gif"><IMG SRC="docs/read_scaling.jpg" BORDER=0 
WIDTH=400 HEIGHT=303 ALT="The Read Throughput Scaling graph reveals the total 
I/O that the system delivers to multiple processes or threads as the number of 
disks in a striped filesystem are varied.  Click on image for a larger 
view."></A></P>
-<B><P>Benchmark Features:</P>
-
-<UL>
-</B><FONT SIZE=2><LI>ANSII C source</FONT> </LI>
-<FONT SIZE=2><LI>POSIX async I/O</FONT> </LI>
-<FONT SIZE=2><LI>Mmap() file I/O</FONT> </LI>
-<FONT SIZE=2><LI>Normal file I/O</FONT> </LI>
-<FONT SIZE=2><LI>Single stream measurement</FONT> </LI>
-<FONT SIZE=2><LI>Multiple stream measurement</FONT> </LI>
-<FONT SIZE=2><LI>POSIX pthreads</FONT> </LI>
-<FONT SIZE=2><LI>Multi-process measurement</FONT> </LI>
-<FONT SIZE=2><LI>Excel importable output for graph generation</FONT> </LI>
-<FONT SIZE=2><LI>Latency plots</FONT> </LI>
-<FONT SIZE=2><LI>64bit compatible source</FONT> </LI>
-<FONT SIZE=2><LI>Large file compatible</FONT> </LI>
-<FONT SIZE=2><LI>Stonewalling in throughput tests to eliminate straggler 
effects</FONT> </LI>
-<FONT SIZE=2><LI>Processor cache size configurable</FONT> </LI>
-<FONT SIZE=2><LI>Selectable measurements with fsync, O_SYNC</FONT> </LI>
-<FONT SIZE=2><LI>Builds for: Linux, HP-UX, IRIX, Solaris, Windows95/98/NT, 
FreeBSD, OpenBSD, OSFV3, OSFV4 </UL>
-</FONT></TD>
-<TD WIDTH="50%" VALIGN="MIDDLE">
-<B><FONT SIZE=2><P>While</B> computers are typically purchased with an 
application in mind it is also likely that over time the application mix will 
change. Many vendors have enhanced their operating systems to perform well for 
some frequently used applications. Although this accelerates the I/O for those 
few applications it is also likely that the system may not perform well for 
other applications that were not targeted by the operating system. An example 
of this type of enhancement is: Database. Many operating systems vendors have 
tested and tuned the filesystem so it works well with databases. While the 
database users are happy, the other users may not be so happy as the entire 
system may be giving all of the system resources to the database users at the 
expense of all other users. As time rolls on the system administrator may 
decide that a few more office automation tasks could be shifted to this 
machine. The load may now shift from a random reader application (database) to 
a se
 quential reader. The users may discover that the machine is very slow when 
running this new application and become dissatisfied with the decision to 
purchase this platform. By using Iozone to get a broad filesystem performance 
coverage the buyer is much more likely to see any hot or cold spots and pick a 
platform and operating system that is more well balanced. </FONT></TD>
-</TR>
-</TABLE>
-</CENTER></P>
-
-<P ALIGN="CENTER"></div><div align="center"></P>
-<P ALIGN="CENTER"><CENTER><TABLE CELLSPACING=0 BORDER=0 CELLPADDING=2 
WIDTH=800>
-<TR><TD WIDTH="50%" VALIGN="MIDDLE">
-<P><A HREF="docs/read_latency.gif"><IMG SRC="docs/read_latency.jpg" BORDER=0 
WIDTH=400 HEIGHT=268 ALT="The NFS3 Read Latency graph shows the latency of 4k 
read operations over an NFS Version 3 filesystem mounted on a client running 
Iozone.  Click on image for a larger view."></A></TD>
-<TD WIDTH="50%" VALIGN="MIDDLE">
-<P><A HREF="docs/reread_latency.gif"><IMG SRC="docs/reread_latency.jpg" 
BORDER=0 WIDTH=400 HEIGHT=272 ALT="The NFS3 Re-read Latency graph shows the 
re-read latency of 4k reads over an NFS Version 3 filesystem.  One can clearly 
see the effects of the client side cache. Here the latencies are the same as 
local buffer cache latencies.  Click on image for larger view."></A></TD>
-</TR>
-</TABLE>
-</CENTER></P>
-
-<P ALIGN="CENTER"></div></P>
-<B><FONT SIZE=2><P>Download Documentation:</B> [ </FONT><A 
HREF="docs/IOzone_msword_98.doc"><FONT SIZE=2>MS Word</FONT></A><FONT SIZE=2> ] 
[ </FONT><A HREF="docs/IOzone_ps.gz"><FONT SIZE=2>Postscript 
gzip</FONT></A><FONT SIZE=2> ] [ </FONT><A HREF="docs/IOzone.htm"><FONT 
SIZE=2>HTML</FONT></A><FONT SIZE=2> ] </P>
-<B><P>Download Source:</B> [</FONT><A HREF="src/current/iozone3_9.tar"><FONT 
SIZE=2>Latest tarball</FONT></A><FONT SIZE=2>] [</FONT><A 
HREF="src/current"><FONT SIZE=2>Latest files</FONT></A><FONT SIZE=2>] 
[</FONT><A HREF="src/stable/iozone3_9.tar"><FONT SIZE=2>Stable 
tarball</FONT></A><FONT SIZE=2> ] [</FONT><A HREF="src/stable"><FONT 
SIZE=2>Stable files</FONT></A><FONT SIZE=2>]</P>
-<B><P>Questions:</B> email </FONT><A 
HREF="mailto:ca...@technologist.com";><FONT 
SIZE=2>ca...@technologist.com</FONT></A><FONT SIZE=2> or </FONT><A 
HREF="mailto:wnorc...@us.oracle.com";><FONT 
SIZE=2>wnorc...@us.oracle.com</FONT></A><FONT SIZE=2> </P>
-</FONT><P><HR></P>
-<FONT SIZE=2><P>Last Updated: <I>Tue Sep 14 12:54:14 EDT 1999</I> </P>
-</FONT><ADDRESS><A HREF="mailto:webmas...@iozone.org";><FONT 
SIZE=2>webmas...@iozone.org</FONT></A><FONT SIZE=2> </ADDRESS></FONT></BODY>
-</HTML>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/iozone3_490/src/current/Changes.txt 
new/iozone3_491/src/current/Changes.txt
--- old/iozone3_490/src/current/Changes.txt     2020-07-13 19:17:40.000000000 
+0200
+++ new/iozone3_491/src/current/Changes.txt     2020-12-14 19:48:51.000000000 
+0100
@@ -2672,5 +2672,8 @@
 Revision 3.490
 Fix compiler warning when HAVE_ANSIC is not defined
 =============================================================================
+Revision 3.491
+Fix CFLAGS issue from Fedora maintainer.
+=============================================================================
 
 
Binary files old/iozone3_490/src/current/fileop and 
new/iozone3_491/src/current/fileop differ
Binary files old/iozone3_490/src/current/fileop_linux-AMD64.o and 
new/iozone3_491/src/current/fileop_linux-AMD64.o differ
Binary files old/iozone3_490/src/current/iozone and 
new/iozone3_491/src/current/iozone differ
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/iozone3_490/src/current/iozone.1 
new/iozone3_491/src/current/iozone.1
--- old/iozone3_490/src/current/iozone.1        2020-07-13 19:17:40.000000000 
+0200
+++ new/iozone3_491/src/current/iozone.1        1970-01-01 01:00:00.000000000 
+0100
@@ -1,531 +0,0 @@
-.TH IOZONE 1
-.SH NAME
-Iozone \- Filesystem Benchmark
-.SH SYNOPSIS
-.B Iozone
-.nh
-[\fB\-a|\-A\fP]
-[\fB\-s\fP \fIfilesize_Kb\fP]
-[\fB\-r\fP \fIrecord_size_Kb\fP]
-[\fB\-f\fP \fI[path]filename\fP]
-[\fB\-i\fP \fItest\fP]
-[\fB\-E\fP]
-[\fB\-p\fP]
-[\fB\-m\fP]
-[\fB\-M\fP]
-[\fB\-t\fP \fIchildren\fP]
-[\fB\-h\fP]
-[\fB\-o\fP]
-[\fB\-l\fP \fImin_number_procs\fP]
-[\fB\-u\fP \fImax_number_procs\fP]
-[\fB\-v\fP]
-[\fB\-R\fP]
-[\fB\-x\fP]
-[\fB\-d\fP \fImicroseconds\fP]
-[\fB\-F\fP \fIpath1 path2...\fP]
-[\fB\-V\fP \fIpattern \fP]
-[\fB\-j\fP \fIstride\fP]
-[\fB\-T\fP]
-[\fB\-C\fP]
-[\fB\-B\fP]
-[\fB\-D\fP]
-[\fB\-G\fP]
-[\fB\-I\fP]
-[\fB\-H\fP \fIdepth\fP]
-[\fB\-k\fP \fIdepth\fP]
-[\fB\-U\fP \fImount_point\fP]
-[\fB\-S\fP \fIcache_size\fP]
-[\fB\-O\fP]
-[\fB\-L\fP \fIline_size\fP]
-[\fB\-K\fP]
-[\fB\-N\fP]
-[\fB\-Q\fP]
-[\fB\-P\fP \fIstart_cpu\fP]
-[\fB\-c\fP]
-[\fB\-e\fP]
-[\fB\-b\fP \fIExcel.xls\fP]
-[\fB\-J\fP \fImilliseconds\fP]
-[\fB\-X\fP \fI[path]filename\fP]
-[\fB\-Y\fP \fI[path]filename\fP]
-[\fB\-w\fP]
-[\fB\-W\fP]
-[\fB\-z\fP]
-[\fB\-Z\fP]
-[\fB\-n\fP \fImin_filesize_Kb\fP]
-[\fB\-g\fP \fImax_filesize_Kb\fP]
-[\fB\-y\fP \fImin_recordsize_Kb\fP]
-[\fB\-q\fP \fImax_recordsize_Kb\fP]
-[\fB\-+d\fP]
-[\fB\-+u\fP]
-[\fB\-+m\fP \fIclient_filename\fP]
-[\fB\-+n\fP]
-[\fB\-+N\fP]
-[\fB\-+p\fP \fIpercent_read\fP]
-[\fB\-+r\fP]
-[\fB\-+t\fP]
-[\fB\-+l\fP]
-[\fB\-+L\fP]
-[\fB\-+D\fP]
-[\fB\-+A\fP \fImadvise_selector\fP]
-[\fB\-+h\fP \fIhostname\fP]
-[\fB\-+T\fP]
-[\fB\-+w\fP \fIPercent de-dupable.\fP]
-
-.hy
-.SH DESCRIPTION
-.B Iozone
-is a filesystem benchmark tool. The benchmark generates and measures
-a variety of file operations. 
-.B Iozone
-has been ported to many machines and runs under many operating systems. 
-This document will cover the many different types of operations that are 
-tested as well as coverage of all of the command line options.
-.PP
-.B Iozone
-is useful for determining a broad filesystem analysis of a vendor's
-computer platform. The benchmark tests file I/O performance for the
-following operations.
-.PP
-          Read, write, re-read, re-write, read backwards, read strided,
-fread, fwrite, random read/write, pread/pwrite variants
-.PP
-While computers are typically purchased with an application in mind it is
-also likely that over time the application mix will change. Many vendors
-have enhanced their operating systems to perform well for some frequently
-used applications. Although this accelerates the I/O for those few
-applications it is also likely that the system may not perform well for
-other applications that were not targeted by the operating system. An
-example of this type of enhancement is: Database. Many operating systems
-have tested and tuned the filesystem so it works well with databases. While
-the database users are happy, the other users may not be so happy as the
-entire system may be giving all of the system resources to the database
-users at the expense of all other users. As time rolls on the system
-administrator may decide that a few more office automation tasks could be
-shifted to this machine. The load may now shift from a random reader
-application (database) to a sequential reader. The users may discover that
-the machine is very slow when running this new application and become
-dissatisfied with the decision to purchase this platform. By using 
-.B Iozone
-to get a broad filesystem performance coverage the buyer is much more likely to
-see any hot or cold spots and pick a platform and operating system that is
-more well balanced.
-
-.SH OPTIONS
-.TP
-.BI \-a
-Used to select full automatic mode. Produces output that covers all tested
-file operations for record sizes of 4k to 16M for file sizes of 64k to 512M.
-.TP
-.BI \-A
-This version of automatic mode provides more coverage but consumes a bunch
-of time.
-The 
-.BI \-a 
-option will automatically stop using transfer sizes less than 64k
-once the file size is 32M or larger. This saves time. The
-.BI \-A 
-option tells 
-.B Iozone
-that you are willing to wait and want dense coverage for small transfers 
-even when the file size is very large.
-.BI NOTE:
-This option is deprecated in
-.BI Iozone
-version 3.61.  Use
-.BI \-az\ \-i\ 0\ \-i\ 1
-instead.
-.TP
-.BI \-b\ filename
-Used to specify a filename that will be used for output
-of an Excel compatible file that contains the results.
-.TP
-.BI \-B
-Use mmap() files. This causes all of the temporary files being measured to
-be created and accessed with the mmap() interface. Some applications prefer 
-to treat files as arrays of memory. These applications mmap() the file 
-and then just access the array with loads and stores to perform file I/O.
-.TP
-.BI \-c
-Include close() in the timing calculations. This is useful only if you
-suspect that close() is broken in the operating system currently under test. 
-It can be useful for NFS Version 3 testing as well to help identify if 
-the nfs3_commit is working well.
-.TP
-.BI \-C
-Show bytes transferred by each child in throughput testing. Useful if your
-operating system has any starvation problems in file I/O or in process 
-management.
-.TP
-.BI \-d\ #
-Microsecond delay out of barrier. During the throughput tests all threads or
-processes are forced to a barrier before beginning the test. Normally, 
-all of the threads or processes are released at the same moment. This 
-option allows one to delay a specified time in microseconds between 
-releasing each of the processes or threads.
-.TP
-.BI \-D
-Use msync(MS_ASYNC) on mmap files. This tells the operating system that all
-the data in the mmap space needs to be written to disk asynchronously.
-.TP
-.BI \-e
-Include flush (fsync,fflush) in the timing calculations
-.TP
-.BI \-E
-Used to select the extension tests. Only available on some platforms. Uses
-pread interfaces.
-.TP
-.BI \-f\ filename
-Used to specify the filename for the temporary file under test. This is
-useful when the unmount option is used. When testing with unmount between
-tests it is necessary for the temporary file under test to be in a 
-directory that can be unmounted. It is not possible to unmount the 
-current working directory as the process 
-.B Iozone
-is running in this directory.
-.TP
-.BI \-F\ filename\ filename\ filename\ ?
-Specify each of the temporary file names to be used in the throughput
-testing. The number of names should be equal to the number of processes or 
-threads that are specified.
-.TP
-.BI \-g\ #
-Set maximum file size (in Kbytes) for auto mode. One may also specify
-.BI \-g\ #k 
-(size in Kbytes) or
-.BI \-g\ #m 
-(size in Mbytes) or
-.BI \-g\ #g
-(size in Gbytes). See
-.BI \-n
-for minimum file size.
-.TP
-.BI \-G
-Use msync(MS_SYNC) on mmap files. This tells the operating system that all
-the data in the mmap space needs to be written to disk synchronously.
-.TP
-.BI \-h
-Displays help screen.
-.TP
-.BI \-H\ #
-Use POSIX async I/O with\ # async operations. 
-.B Iozone
-will use POSIX async I/O with a bcopy from the async buffers back into the 
-applications buffer. Some versions of MSC NASTRAN perform I/O this way. 
-This technique is used by applications so that the async I/O may be performed 
-in a library and requires no changes to the applications internal model.
-.TP
-.BI \-i\ #
-Used to specify which tests to run. (0=write/rewrite, 1=read/re-read,
-2=random-read/write, 3=Read-backwards, 4=Re-write-record,
-5=stride-read, 6=fwrite/re-fwrite, 7=fread/Re-fread,
-8=mixed workload, 9=pwrite/Re-pwrite, 10=pread/Re-pread, 11=pwritev/Re-pwritev,
-12=preadv/Re-preadv). 
-One will always need to specify 0 so that any of the following tests will
-have a file to measure.
-.BI -i\ #\ -i\ #\ -i\ #
-is also supported so that one may select more than one test.
-.TP
-.BI \-I
-Use DIRECT IO if possible for all file operations. Tells the filesystem that
-all operations to the file are to bypass the buffer cache and go directly to 
-disk. (not available on all platforms)
-.TP
-.BI \-j\ #
-Set stride of file accesses to (# * record size). The stride read test will
-read records at this stride.
-.TP
-.BI \-J\ #
-Millisecond delay before each I/O operation. This simulates the
-cpu compute cycle of an application that precedes an I/O operation.
-One may also use
-.BI \-X
-or
-.BI \-Y
-to control the compute cycle on a per I/O operation basis.
-.TP
-.BI \-k\ #
-Use POSIX async I/O (no bcopy) with\ # async operations. 
-.B Iozone
-will use POSIX async I/O and will not perform any extra bcopys. The buffers 
-used by 
-.B Iozone 
-will be handed to the async I/O system call directly.
-.TP
-.BI \-K
-Inject some random accesses in the testing. 
-.TP
-.BI \-l\ #
-Set the lower limit on number of processes to run. When running throughput
-tests this option allows the user to specify the least number of processes 
-or threads to start. This option should be used in conjunction with 
-the
-.BI \-u
-option.
-.TP
-.BI \-L\ #
-Set processor cache line size to value (in bytes). Tells 
-.B Iozone 
-the processor cache line size.  This is used internally to help speed up 
-the test.
-.TP
-.BI \-m
-Tells 
-.B Iozone
-to use multiple buffers internally. Some applications read into a single
-buffer over and over. Others have an array of buffers. This option allows
-both types of applications to be simulated. 
-.B Iozone\'s 
-default behavior is to re-use internal buffers. This option allows one 
-to override the default and to use multiple internal buffers.
-.TP
-.BI \-M
-\.B
-Iozone
-will call uname() and will put the string in the output file.
-.TP
-.BI \-n\ #
-Set minimum file size (in Kbytes) for auto mode. One may also specify
-.BI \-n\ #k 
-(size in Kbytes) or
-.BI \-n\ #m 
-(size in Mbytes) or
-.BI \-n\ #g
-(size in Gbytes). See
-.BI \-g
-for maximum file size.
-.TP
-.BI \-N
-Report results in microseconds per operation.
-.TP
-.BI \-o
-Writes are synchronously written to disk. (O_SYNC). 
-.B Iozone
-will open the files with the O_SYNC flag. This forces all writes to the 
-file to go completely to disk before returning to the benchmark.
-.TP
-.BI \-O
-Give results in operations per second.
-.TP
-.BI \-p
-This purges the processor cache before each file operation. 
-.B Iozone
-will allocate another internal buffer that is aligned to the same 
-processor cache boundary and is of a size that matches the processor cache. 
-It will zero fill this alternate buffer before beginning each test.
-This will purge the processor cache and allow one to see the memory
-subsystem without the acceleration due to the processor cache.
-.TP
-.BI \-P\ #
-Bind processes/threads to processors, starting with this cpu\ #. Only
-available on some platforms. The first sub process or thread will begin 
-on the specified processor. Future processes or threads will be placed on
-the next processor. Once the total number of cpus is exceeded then
-future processes or threads will be placed in a round robin
-fashion.
-.TP
-.BI \-q\ #
-Set maximum record size (in Kbytes) for auto mode. One may also specify
-.BI \-q\ #k 
-(size in Kbytes) or
-.BI \-q\ #m 
-(size in Mbytes) or
-.BI \-q\ #g
-(size in Gbytes). See
-.BI \-y
-for minimum record size.
-.TP
-.BI \-Q
-Create offset/latency files. 
-.B Iozone
-will create latency versus offset data files that can be imported with a 
-graphics package and plotted. This is useful for finding if certain offsets
-have very high latencies. Such as the point where UFS will allocate its
-first indirect block.  One can see from the data the impacts of the extent 
-allocations for extent based filesystems with this option.
-.TP
-.BI \-r\ #
-Used to specify the record size, in Kbytes, to test. One may also specify
-.BI \-r\ #k 
-(size in Kbytes) or
-.BI \-r\ #m 
-(size in Mbytes) or
-.BI \-r\ #g
-(size in Gbytes).
-.TP
-.BI \-R
-Generate Excel report. 
-.B Iozone
-will generate an Excel compatible report to standard out. This
-file may be imported with Microsoft Excel (space delimited) and used to
-create a graph of the filesystem performance. Note: The 3D graphs are 
-column oriented. You will need to select this when graphing as the 
-default in Excel is row oriented data.
-.TP
-.BI \-s\ #
-Used to specify the size, in Kbytes, of the file to test. One may also
-specify
-.BI \-s\ #k 
-(size in Kbytes) or 
-.BI \-s\ #m 
-(size in Mbytes) or
-.BI \-s\ #g
-(size in Gbytes).
-.TP
-.BI \-S\ #
-Set processor cache size to value (in Kbytes). This tells 
-.B Iozone
-the size of the processor cache.  It is used internally for buffer alignment 
-and for the purge functionality.
-.TP
-.BI \-t\ #
-Run 
-.B Iozone
-in a throughput mode. This option allows the user to specify how
-many threads or processes to have active during the measurement.
-.TP
-.BI \-T
-Use POSIX pthreads for throughput tests. Available on platforms that have
-POSIX threads.
-.TP
-.BI \-u\ #
-Set the upper limit on number of processes to run. When running throughput
-tests this option allows the user to specify the greatest number of 
-processes or threads to start. This option should be used in conjunction 
-with the
-.BI \-l
-option.
-.TP
-.BI \-U\ mountpoint
-Mount point to unmount and remount between tests. 
-.B Iozone
-will unmount and remount this
-mount point before beginning each test. This guarantees that the buffer
-cache does not contain any of the file under test.
-.TP
-.BI \-v 
-Display the version of 
-.B Iozone.
-.TP
-.BI \-V\ #
-Specify a pattern that is to be written to the temporary file and validated
-for accuracy in each of the read tests.
-.TP
-.BI \-w
-Do not unlink temporary files when finished using them.
-.TP
-.BI \-W
-Lock file when reading or writing.
-.TP
-.BI \-x
-Turn off stone-walling. Stonewalling is a technique used internally to
-.B Iozone.
-It is used during the throughput tests. The code starts all threads or 
-processes and then stops them on a barrier.  Once they are all ready to 
-start then they are all released at the same time. The moment that
-any of the threads or processes finish their work then the entire test is
-terminated and throughput is calculated on the total I/O that was 
-completed up to this point. This ensures that the entire measurement was 
-taken while all of the processes or threads were running in parallel. 
-This flag allows one to turn off the stonewalling and see what happens.
-.TP
-.BI \-X\ filename
-Used to specify a filename that will be used for the 
-write telemetry information. The file contains lines
-with offset, size, delay_in_milliseconds. Each of 
-these lines are used to perform an I/O operation. 
-This is used when an application's specific I/O operations
-are known, and one wishes to benchmark the system 
-with this specific application file behavior.
-.TP
-.BI \-y\ #
-Set minimum record size (in Kbytes) for auto mode. One may also specify
-.BI \-y\ #k 
-(size in Kbytes) or
-.BI \-y\ #m 
-(size in Mbytes) or
-.BI \-y\ #g
-(size in Gbytes). See
-.BI \-q
-for maximum record size.
-.TP
-.BI \-Y\ filename
-Used to specify a filename that will be used for the 
-read telemetry information. The file contains lines
-with offset, size, delay_in_milliseconds. Each of 
-these lines are used to perform an I/O operation. 
-This is used when an application's specific I/O operations
-are known, and one wishes to benchmark the system 
-with this specific application file behavior.
-.TP
-.BI \-z
-Used in conjunction with
-.BI \-a
-to test all possible record sizes. Normally
-.BI Iozone
-omits testing of small record sizes for very large files
-when used in full automatic mode. This option forces
-.BI Iozone
-to include the small record sizes in the automatic tests also.
-.TP
-.BI \-Z
-Enable mixing of mmap I/O and file I/O.
-.TP
-.BI \-+m\ filename
-Used to specify a filename that will be used to specify
-the clients in a distributed measurement. The file
-contains one line for each client. The fields are 
-space delimited. Field 1 is the client name. Field 2
-is the working directory, on the client, where Iozone
-will run. Field 3 is the path to the executable Iozone
-on the client.
-.TP
-.BI \-+n
-No retests selected. Used to prevent retests from running.
-.TP
-.BI \-+N
-No truncating or deleting of previous test file before the sequential write 
test. Useful only after -w is used in previous command to leave the test file 
in place for reuse.  This flag is of limited use, when a single retest is not 
enough, or to easily control when sequential write retests occur without file 
truncation or deletion.
-.TP
-.BI \-+u
-Used to enable CPU statistics collection.
-.TP
-.BI \-+d 
-Diagnostic mode to troubleshoot a broken file I/O subsystem.
-.TP
-.BI \-+p\  percentage_reads
-Used to set the percentage of threads/processes that will perform read
-testing in the mixed workload test case.
-.TP
-.BI \-+r
-Enable O_RSYNC | O_SYNC on all testing. 
-.TP
-.BI \-+l
-Enable byte range locking.
-.TP
-.BI \-+L
-Enable byte range locking & shared file mode.
-.TP
-.BI \-+D
-Enable O_DSYNC on all testing. 
-.TP
-.BI \-+t
-Enable network performance test. Use with -+m
-.TP
-.BI \-+A #
-Enable madvise behavior. 0 = normal, 1=random, 2=sequential, 3=dontneed, 
4=willneed
-.TP
-.BI \-+B
-Enable sequential mixed workload testing.
-.TP
-.BI \-+T
-Enable time stamps logging.
-.TP
-.BI \-+h
-Manually set hostname.
-.TP
-.BI \-+w #
-Percentage of data to be de-dupable between files.
-
-.SH AUTHOR
-Original Author: William D. Norcott. wnorc...@us.oracle.com
-
-Features & extensions: Don Capps ca...@iozone.org
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/iozone3_490/src/current/iozone.c 
new/iozone3_491/src/current/iozone.c
--- old/iozone3_490/src/current/iozone.c        2020-07-13 19:17:40.000000000 
+0200
+++ new/iozone3_491/src/current/iozone.c        2021-01-13 00:03:49.000000000 
+0100
@@ -60,7 +60,7 @@
 
 
 /* The version number */
-#define THISVERSION "        Version $Revision: 3.489 $"
+#define THISVERSION "        Version $Revision: 3.491 $"
 
 #if defined(Windows)
 #define NO_THREADS
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/iozone3_490/src/current/iozone.tar 
new/iozone3_491/src/current/iozone.tar
--- old/iozone3_490/src/current/iozone.tar      2021-01-25 18:21:00.296204890 
+0100
+++ new/iozone3_491/src/current/iozone.tar      1970-01-01 01:00:00.000000000 
+0100
@@ -1 +0,0 @@
-symbolic link to iozone3_490.tar
Binary files old/iozone3_490/src/current/iozone3_490.tar and 
new/iozone3_491/src/current/iozone3_490.tar differ
Binary files old/iozone3_490/src/current/iozone_linux-AMD64.o and 
new/iozone3_491/src/current/iozone_linux-AMD64.o differ
Binary files old/iozone3_490/src/current/libasync.o and 
new/iozone3_491/src/current/libasync.o differ
Binary files old/iozone3_490/src/current/libbif.o and 
new/iozone3_491/src/current/libbif.o differ
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/iozone3_490/src/current/makefile 
new/iozone3_491/src/current/makefile
--- old/iozone3_490/src/current/makefile        2020-07-13 19:17:40.000000000 
+0200
+++ new/iozone3_491/src/current/makefile        2021-01-13 00:36:48.000000000 
+0100
@@ -1,5 +1,5 @@
 #
-# Version $Revision: 1.155 $
+# Version $Revision: 1.156 $
 #
 # The makefile for building all versions of iozone for all supported
 # platforms
@@ -14,7 +14,7 @@
 GCC    = gcc
 CCS    = /usr/ccs/bin/cc
 NACC   = /opt/ansic/bin/cc
-CFLAGS =
+CFLAGS ?=
 S10GCCFLAGS    = -m64
 S10CCFLAGS     = -m64
 FLAG64BIT      = -m64
@@ -94,8 +94,8 @@
        rm -f *.o iozone fileop pit_server
 
 rpm:
-       cp ../../iozone*.tar /usr/src/red*/SO*
-       rpmbuild -ba spec.in
+       cp ../../iozone*.tar /home/capps/rpmbuild/SOURCES/
+       rpmbuild  -ba --buildroot /home/capps/rpmbuild/BUILDROOT spec.in
 
 
 #
@@ -172,10 +172,10 @@
 # GNU 'C' compiler Linux build with threads, largefiles, async I/O 
 #
 linux: iozone_linux.o libasync.o libbif.o fileop_linux.o pit_server.o
-       $(CC)  -O3 $(LDFLAGS) iozone_linux.o libasync.o libbif.o -lpthread \
+       $(CC)  -O3 $(CFLAGS) iozone_linux.o libasync.o libbif.o -lpthread \
                -lrt -o iozone
-       $(CC)  -O3 -Dlinux fileop_linux.o -o fileop
-       $(CC)  -O3 -Dlinux pit_server.o -o pit_server
+       $(CC)  -O3 $(CFLAGS) -Dlinux fileop_linux.o -o fileop
+       $(CC)  -O3 $(CFLAGS) -Dlinux pit_server.o -o pit_server
 
 #
 # GNU 'C' compiler Linux build for powerpc chip with threads, largefiles, 
async I/O 
Binary files old/iozone3_490/src/current/pit_server and 
new/iozone3_491/src/current/pit_server differ
Binary files old/iozone3_490/src/current/pit_server.o and 
new/iozone3_491/src/current/pit_server.o differ
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/iozone3_490/src/current/spec.in 
new/iozone3_491/src/current/spec.in
--- old/iozone3_490/src/current/spec.in 2020-07-13 19:17:40.000000000 +0200
+++ new/iozone3_491/src/current/spec.in 2020-12-14 19:48:51.000000000 +0100
@@ -1,7 +1,7 @@
 Summary: Iozone Filesystem Benchmark
 Name: iozone
 Version: 3
-Release: 490
+Release: 491
 License: Freeware
 Group: Applications/Engineering
 Source: %{name}%{version}_%{release}.tar
@@ -25,7 +25,7 @@
 ##
 ## SETUP and PATCH
 ##
-%setup -n iozone3_490/src/current
+%setup -n iozone3_491/src/current
 
 
 ##
@@ -75,22 +75,22 @@
 ##
 %install
 mkdir -p $RPM_BUILD_ROOT/opt/iozone/bin
-cp $RPM_BUILD_DIR/iozone3_490/src/current/iozone 
$RPM_BUILD_ROOT/opt/iozone/bin/
-cp $RPM_BUILD_DIR/iozone3_490/src/current/fileop 
$RPM_BUILD_ROOT/opt/iozone/bin/
-cp $RPM_BUILD_DIR/iozone3_490/src/current/pit_server 
$RPM_BUILD_ROOT/opt/iozone/bin/
-cp $RPM_BUILD_DIR/iozone3_490/src/current/Generate_Graphs 
$RPM_BUILD_ROOT/opt/iozone/bin/
-cp $RPM_BUILD_DIR/iozone3_490/src/current/gengnuplot.sh 
$RPM_BUILD_ROOT/opt/iozone/bin/
-cp $RPM_BUILD_DIR/iozone3_490/src/current/gnu3d.dem 
$RPM_BUILD_ROOT/opt/iozone/bin/
+cp $RPM_BUILD_DIR/iozone3_491/src/current/iozone 
$RPM_BUILD_ROOT/opt/iozone/bin/
+cp $RPM_BUILD_DIR/iozone3_491/src/current/fileop 
$RPM_BUILD_ROOT/opt/iozone/bin/
+cp $RPM_BUILD_DIR/iozone3_491/src/current/pit_server 
$RPM_BUILD_ROOT/opt/iozone/bin/
+cp $RPM_BUILD_DIR/iozone3_491/src/current/Generate_Graphs 
$RPM_BUILD_ROOT/opt/iozone/bin/
+cp $RPM_BUILD_DIR/iozone3_491/src/current/gengnuplot.sh 
$RPM_BUILD_ROOT/opt/iozone/bin/
+cp $RPM_BUILD_DIR/iozone3_491/src/current/gnu3d.dem 
$RPM_BUILD_ROOT/opt/iozone/bin/
 
 mkdir -p $RPM_BUILD_ROOT/opt/iozone/docs
-cp $RPM_BUILD_DIR/iozone3_490/docs/IOzone_msword_98.pdf 
$RPM_BUILD_ROOT/opt/iozone/docs/
-cp $RPM_BUILD_DIR/iozone3_490/docs/Run_rules.doc 
$RPM_BUILD_ROOT/opt/iozone/docs/
-cp $RPM_BUILD_DIR/iozone3_490/docs/IOzone_msword_98.doc 
$RPM_BUILD_ROOT/opt/iozone/docs/
-cp $RPM_BUILD_DIR/iozone3_490/docs/Iozone_ps.gz 
$RPM_BUILD_ROOT/opt/iozone/docs/
-cp $RPM_BUILD_DIR/iozone3_490/src/current/Gnuplot.txt 
$RPM_BUILD_ROOT/opt/iozone/docs/
+cp $RPM_BUILD_DIR/iozone3_491/docs/IOzone_msword_98.pdf 
$RPM_BUILD_ROOT/opt/iozone/docs/
+cp $RPM_BUILD_DIR/iozone3_491/docs/Run_rules.doc 
$RPM_BUILD_ROOT/opt/iozone/docs/
+cp $RPM_BUILD_DIR/iozone3_491/docs/IOzone_msword_98.doc 
$RPM_BUILD_ROOT/opt/iozone/docs/
+cp $RPM_BUILD_DIR/iozone3_491/docs/Iozone_ps.gz 
$RPM_BUILD_ROOT/opt/iozone/docs/
+cp $RPM_BUILD_DIR/iozone3_491/src/current/Gnuplot.txt 
$RPM_BUILD_ROOT/opt/iozone/docs/
 
 mkdir -p $RPM_BUILD_ROOT/opt/iozone/man/man1
-cp $RPM_BUILD_DIR/iozone3_490/docs/iozone.1 
$RPM_BUILD_ROOT/opt/iozone/man/man1/
+cp $RPM_BUILD_DIR/iozone3_491/docs/iozone.1 
$RPM_BUILD_ROOT/opt/iozone/man/man1/
 
 
 ##

Reply via email to