From: Sedat Dilek <sedat.dilek@gmail.com>
To: Dongsheng Song <dongsheng.song@gmail.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Guillem Jover <guillem@debian.org>,
linux-aio <linux-aio@kvack.org>,
Benjamin LaHaise <bcrl@kvack.org>
Subject: Re: libaio tarballs on <kernel.org>
Date: Sun, 4 Jan 2015 11:02:46 +0100 [thread overview]
Message-ID: <CA+icZUVwmQkArRF2mtnF_JrTE8tueuejesawF-gu4xzKddpSTQ@mail.gmail.com> (raw)
In-Reply-To: <CAE8XmWo-fOG1jEFPD4oFbR68Oaky+cUwvgVzEar2cfH7k4c1xQ@mail.gmail.com>
On Sun, Jan 4, 2015 at 9:55 AM, Dongsheng Song <dongsheng.song@gmail.com> wrote:
> On Sun, Jan 4, 2015 at 4:21 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> I have also seen... with outdated material?
>>
>
> we can use syscall.h and aio_abi.h directly.
>
> IMHO, I think libaio is of little value. It's just simple wrappers of
> aio syscall and some useful macros. It will useful only when it
> implement posix aio api, but this only on the roadmap.
Thanks for your feedback.
The background of my asking was that I wanted a higher version of
libaio-dev which is a prereq for fio on Ubuntu/precise for my tests
with loop-mq feature.
Cannot say if it is possible to build with syscall.h and aio_abi.h
directly (shipped with the Linux-kernel sources which might change
from release to release).
- Sedat -
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2015-01-04 10:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 21:23 libaio tarballs on <kernel.org> Sedat Dilek
2015-01-04 8:21 ` Sedat Dilek
2015-01-04 8:55 ` Dongsheng Song
2015-01-04 10:02 ` Sedat Dilek [this message]
2015-01-05 1:50 ` Dongsheng Song
2015-01-05 19:01 ` Jeff Moyer
2015-01-05 19:13 ` Sedat Dilek
2015-01-05 19:17 ` Jeff Moyer
2015-01-05 21:54 ` Henrique de Moraes Holschuh
2015-01-05 22:02 ` Sedat Dilek
2015-01-04 17:45 ` Guillem Jover
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=CA+icZUVwmQkArRF2mtnF_JrTE8tueuejesawF-gu4xzKddpSTQ@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=bcrl@kvack.org \
--cc=dongsheng.song@gmail.com \
--cc=guillem@debian.org \
--cc=jmoyer@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).