All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Tom <4711@gnurz.de>
Cc: fio@vger.kernel.org
Subject: Re: Fio on solaris
Date: Mon, 23 Nov 2009 17:24:34 +0100	[thread overview]
Message-ID: <20091123162433.GI8742@kernel.dk> (raw)
In-Reply-To: <53558.194.113.141.20.1258991444.squirrel@webmail.s-itc.de>

On Mon, Nov 23 2009, Tom wrote:
> Thanks Jens!
> now it's possible to compile that, but (yes, we've a "but"), when I call:
> 
> > fio four_threads.fio
> fio: engine libaio not loadable
> fio: failed to load engine libaio
> fio: file:ioengines.c:98, func=dlopen, error=ld.so.1: fio: fatal: libaio:
> open failed: No such file or directory
> 
> I search for that libaio and found it
> 
> > ll    /usr/lib/libaio.so*
> lrwxrwxrwx   1 root     root          21 Sep  4 10:28 /usr/lib/libaio.so
> -> ../../lib/libaio.so.1
> lrwxrwxrwx   1 root     root          21 Sep  4 10:28 /usr/lib/libaio.so.1
> -> ../../lib/libaio.so.1
> 
> > ll /lib/libaio.so*
> lrwxrwxrwx   1 root     root          11 Sep  4 10:34 /lib/libaio.so ->
> libaio.so.1
> -rwxr-xr-x   1 root     bin        46452 Feb 12  2009 /lib/libaio.so.1
> 
> but that on isn't the right one?
> 
> What kind of libaio have you installed at your SUN where ist it from? We
> have looked around. For Linux we found tonns of libaio and libaio-devel,
> but nothing for SUN.

The libaio engine is Linux specific. On Solaris, the available async
engines are posixaio and the native solarisaio.

-- 
Jens Axboe


      reply	other threads:[~2009-11-23 16:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19  9:39 Fio on solaris Tom
2009-11-19 20:14 ` Jens Axboe
2009-11-23 12:03   ` Jens Axboe
2009-11-23 12:13     ` Tom
2009-11-23 12:14       ` Jens Axboe
2009-11-23 12:51         ` Tom
2009-11-23 12:59           ` Jens Axboe
2009-11-23 13:21             ` Tom
2009-11-23 14:19               ` Jens Axboe
2009-11-23 15:50                 ` Tom
2009-11-23 16:24                   ` 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=20091123162433.GI8742@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=4711@gnurz.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 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.