From: "Richard W.M. Jones" <rjones@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: fio <fio@vger.kernel.org>
Subject: Re: [PATCH, RFC] list all available dynamic ioengines with --enghelp
Date: Mon, 9 Nov 2020 14:36:16 +0000 [thread overview]
Message-ID: <20201109143616.GB9867@redhat.com> (raw)
In-Reply-To: <b1864b03-e0fe-2ffd-7a33-5875b3c31760@sandeen.net>
On Sat, Nov 07, 2020 at 12:15:18PM -0600, Eric Sandeen wrote:
> On 11/6/20 4:07 PM, Eric Sandeen wrote:
> > When dynamic engines are enabled, "fio --enghelp" does not list all
> > available engines as the man page says it will:
> >
> > If no ioengine is given, list all available ioengines.
> >
> > Fix this by opening FIO_EXT_ENG_DIR and attempting dlopen_ioengine
> > everything that's found there.
>
> The last(?) thing that would be nice to fix for the dynamic engines is to
> not hardcode FIO_EXT_ENG_DIR to /usr/lib/fio since many systems will
> be using /usr/lib64, but I'm not really sure how to do that best in
> the hardcoded configure world of fio ... I could hack something up.
Not to mention FreeBSD which seems to be using /usr/local/lib, or
would do if they had enabled the modules
(https://www.freshports.org/benchmarks/fio/).
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
prev parent reply other threads:[~2020-11-09 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 22:07 [PATCH, RFC] list all available dynamic ioengines with --enghelp Eric Sandeen
2020-11-07 18:15 ` Eric Sandeen
2020-11-09 14:36 ` Richard W.M. Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201109143616.GB9867@redhat.com \
--to=rjones@redhat.com \
--cc=fio@vger.kernel.org \
--cc=sandeen@sandeen.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox