All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@gmail.com>
To: "Michal Šmucr" <msmucr@gmail.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>,
	Bruce Cran <bruce@cran.org.uk>
Subject: Re: missing waitpid() and server functionality at Windows
Date: Mon, 31 Jul 2017 07:10:31 +0100	[thread overview]
Message-ID: <CALjAwxhNLWRJq_A8nD0=VCo0r-FBywB4XTrC-PBakuunCUOkHA@mail.gmail.com> (raw)
In-Reply-To: <56BA67C0.1030603@gmail.com>

I've only just noticed this slipped by without reply - sorry this took so long!

On 9 February 2016 at 22:27, Michal Šmucr <msmucr@gmail.com> wrote:
>
> previously I've used fio mainly at Linux and OS X, so I didn't have any
> issues with fio in server mode. Now I'm trying to simulate workload to
> shared storage for Windows clients and this functionality with remote
> control of fio instances running at Windows machines will be very handy.
> Unfortunately it isn't possible to use it that way, because of missing
> waitpid() syscall implementation and forking in MinGw builds for Windows.
>
> I've stumbled upon at some messages posted 2y ago, where Bruce explained it.
> http://www.spinics.net/lists/fio/msg02565.html
>
> I don't know, if I got it correctly, but can be a build with Cygwin
> toolchain possible workaround for this issue?
> I've tried to compile current fio with Cygwin (so no MinGw toolchain) and
> compiler variables override, but failed badly.. It doesn't even pass through
> crc/test.c with lot of messed definitions. Is it currently possible to build
> with it or MinGW is currently only way for Windows compilation of fio?

Even at the time of writing fio does not build in a "full" Cygwin
environment. It actually tries to be a native Windows program (hence
MinGW) so it can access native Windows calls (rather than Cygwin ones)
and not carry the Cygwin portability library. I suppose someone could
undertake such a port but it would be nicer if server mode could be
made to work with threads (but that's also new work someone would have
to perform).

-- 
Sitsofe | http://sucs.org/~sits/

      reply	other threads:[~2017-07-31  6:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 22:27 missing waitpid() and server functionality at Windows Michal Šmucr
2017-07-31  6:10 ` Sitsofe Wheeler [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='CALjAwxhNLWRJq_A8nD0=VCo0r-FBywB4XTrC-PBakuunCUOkHA@mail.gmail.com' \
    --to=sitsofe@gmail.com \
    --cc=bruce@cran.org.uk \
    --cc=fio@vger.kernel.org \
    --cc=msmucr@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.