Flexible I/O Tester development
 help / color / mirror / Atom feed
From: "Stefan Hübner" <shu@wwwgroup.de>
To: fio@vger.kernel.org
Subject: Windows & netio problems/bugreport
Date: Tue, 18 Sep 2012 10:30:47 +0000	[thread overview]
Message-ID: <DIIE.000011B400039534@192.168.0.5> (raw)

Hello Bruce,

I just noticed a major bug in fio for windows (proven on W7 and WSS 2008R2).  It seems the netio-testing doesn't work at all a.t.m, even with elevated privileges.

C:\Program Files\fio\examples>..\fio.exe netio
receiver: (g=0): rw=read, bs=4K-4K/4K-4K, ioengine=net, iodepth=1
sender: (g=0): rw=write, bs=4K-4K/4K-4K, ioengine=net, iodepth=1
fio-2.0.9
Starting 2 threads
fio: pid=2644, err=1/file:engines/net.c:631, func=socket, error=No error
Jobs: 1 (f=0): [XW] [0.0% done] [0K/0K /s] [0 /0  iops] [eta 49710d:06h:19m:22s]
C:\Program Files\fio\examples>

This happened when testing the example "netio" taskfile.  I've written own taskfiles where I get the same error.

corresponding code:
static int fio_netio_setup_listen_inet(struct thread_data *td, short port)
{
        struct netio_data *nd = td->io_ops->data;
        struct netio_options *o = td->eo;
        int fd, opt, type;

        if (o->proto == FIO_TYPE_TCP)
                type = SOCK_STREAM;
        else
                type = SOCK_DGRAM;

-->     fd = socket(AF_INET, type, 0);
        if (fd < 0) {
                td_verror(td, errno, "socket");
                return 1;
        }
[...]

May this mean the "socket()" function needs to be used differently in Windows?  Can you put a "FixIt" on your ToDo-List for this?

all the best,
Stefan

             reply	other threads:[~2012-09-18 10:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 10:30 Stefan Hübner [this message]
2012-10-10 12:27 ` Windows & netio problems/bugreport Bruce Cran
2012-10-10 15:07   ` Jens Axboe

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=DIIE.000011B400039534@192.168.0.5 \
    --to=shu@wwwgroup.de \
    --cc=fio@vger.kernel.org \
    /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