On 2020/01/20 16:22, Kurt Miller wrote:
> fio is a IO benchmarking tool that can simulate various user defined
> workloads. fio will spawn a number of threads or processes doing a
> particular type of IO action as specified by the user. It takes a
> number of global parameters, each inherited by the thread unless other
> parameters given to them overriding that setting. The typical use of
> fio is to write a job file matching the IO load one wants to simulate.
>
> tested on aarch64/amd64/i386
>
> okay?
: DPB_PROPERTIES= parallel
I don't feel strongly either way, but that's usually only done for
fairly large ports, or ones on the path to something that blocks a lot
of other ports.
: COMMENT= flexible I/O tester
:
: GH_ACCOUNT= axboe
: GH_PROJECT= fio
: GH_TAGNAME= fio-3.17
: PKGNAME= ${GH_TAGNAME}
:
: CATEGORIES= benchmarks
:
: HOMEPAGE= https://github.com/axboe/fio
https://fio.readthedocs.io/ might be better?
:
: MAINTAINER= Kurt Miller <k...@openbsd.org>
:
: # GPLv2+
It's GPLv2 only. The author also requests that any published results
mention that fio was used and which version (MORAL-LICENSE in the
distribution), it might be nice to add a quick note about that to the
comment?
: PERMIT_PACKAGE= Yes
:
: WANTLIB= c m pthread z
:
: USE_GMAKE= Yes
: SEPARATE_BUILD= Yes
:
: CONFIGURE_STYLE=simple
:
: .include <bsd.port.mk>
Hidden behind the pretty-printed "CC <filename>" lines it uses
-march=native (which is no good for package builds) and -O3. Could you
add these please so it displays the commands and honours CFLAGS?
MAKE_FLAGS= V=1 \
EXTFLAGS="${CFLAGS}"
CONFIGURE_ARGS= --disable-optimizations \
--disable-native
OK with those or similar.
