From: Jens Axboe <axboe@kernel.dk>
To: Martin Steigerwald <ms@teamix.de>
Cc: fio@vger.kernel.org
Subject: Re: relationship of fio versus gfio
Date: Tue, 10 Nov 2015 08:20:44 -0700 [thread overview]
Message-ID: <56420B4C.2040708@kernel.dk> (raw)
In-Reply-To: <2367452.mALFllXUSD@merkaba>
On 11/10/2015 03:25 AM, Martin Steigerwald wrote:
> Am Montag, 9. November 2015, 15:01:04 CET schrieb Jens Axboe:
>> On 11/06/2015 01:54 AM, Martin Steigerwald wrote:
>>> Hello Jens, hello fio community.
>>>
>>> During package review of my new fio package my reviewer raised the
>>> question of the relationship between gfio and fio. I already also
>>> wondered about it before.
>>>
>>> Can gfio be used on a system, without fio installed? My guess would be
>>> yes: As fio could be running on another machine as a server.
>>
>> That is correct.
>
> Thanks. My sponsor Sven just uploaded the debian package to unstable.
>
>>
>>> Also currently I have it that gfio is linked against the same libraries as
>>> fio. Is a complete fio engine included in gfio?
>>
>> There was a plan to more cleanly separate them, as the client frontends
>> need not link with all the nitty gritty details as the backend. But the
>> amount of effort required to get that cleaner meant that it didn't
>> really happen. It's not difficult, it's just a lot of manual work in
>> establishing the code boundaries between the two.
>
> I see.
>
> I also wondered about doing some Qt Quick based frontend for fio, but never
> got along starting it. Also it would be redoing work that is already done
> (gfio).
That'd be great, though. gtk isn't very portable, one of the goals of
the gui frontend was to have something that people on OSX/Windows could
also use without having to resort to a command line.
--
Jens Axboe
prev parent reply other threads:[~2015-11-10 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 8:54 relationship of fio versus gfio Martin Steigerwald
2015-11-09 22:01 ` Jens Axboe
2015-11-10 10:25 ` Martin Steigerwald
2015-11-10 15:20 ` Jens Axboe [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=56420B4C.2040708@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=ms@teamix.de \
/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