From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: vikas gupta <vikas_gupta51013@yahoo.co.in>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org, bcrl@kvack.org
Subject: Re: AIO Support and related package information??
Date: Mon, 26 Sep 2005 10:59:51 +0200 [thread overview]
Message-ID: <1127725191.2069.17.camel@frecb000686> (raw)
In-Reply-To: <20050926073220.55509.qmail@web8405.mail.in.yahoo.com>
On Mon, 2005-09-26 at 08:32 +0100, vikas gupta wrote:
> hi Sebastien ,
>
> I am having yet another query related to AIO Support
>
> 1)As you mentioned that aio posix support is provided
> by glibc also so can you tell me on the performance
> basis which one is better (glibc implementation or
> libposix implementation ) and how do we measure the
> performance
Have a look at:
http://www.bullopensource.org/posix/Bench/sysbench-oltp/sysbench.html
for benchmarks using Sysbench and MySQL.
>
> I have compiled glibc with following command
>
> gcc -g $1.c -o $1 -lrt -lpthread
Then you're using glibc AIO implementation based on helper threads
and without taking advantage of kernel support.
>
>
> 2)What posix features is supported by bare kernel and
> libposix implementation, without applying the
> patches.I have broken down my query in following
> parts
Without any of the patches:
>
> 2.1) aio_read/aio_write is supported but what
> limitation are there
Supported but without notification (SIGEV_NONE only).
>
> 2.2) aio_fsync is supported or not
Supported only if the underlying fs implements it
>
> 2.3) what are the limitation with lio_listio
Not supported wihtout the patches.
>
> 2.4) what are the additional feature it provides for
> aio_cancel implementation
>
Needs support from the underlying fs.
>
> 3) Is glibc implementation is providing all the above
> mentioned fetures
Yes, I think so.
>
> 4) Is there any test program that can measure
> efficiency for both glibc and libposix implementation
I personally use Sysbench and have compiled 3 MySQL servers,
one with librt AIO, one with libposix-aio and one with MySQL
native simulated AIO.
You may also try iozone.
>
>
> With Thanks in advance
> Vikas
Hope this helps,
Sébastien.
--
------------------------------------------------------
Sébastien Dugué BULL/FREC:B1-247
phone: (+33) 476 29 77 70 Bullcom: 229-7770
mailto:sebastien.dugue@bull.net
Linux POSIX AIO: http://www.bullopensource.org/posix
------------------------------------------------------
next prev parent reply other threads:[~2005-09-26 8:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 3:08 AIO Support and related package information?? vikas gupta
2005-09-22 7:46 ` Sébastien Dugué
2005-09-23 3:10 ` vikas gupta
2005-09-23 7:05 ` Sébastien Dugué
2005-09-26 7:32 ` vikas gupta
2005-09-26 8:59 ` Sébastien Dugué [this message]
2005-09-26 9:13 ` vikas gupta
2005-09-26 13:45 ` Sébastien Dugué
2005-09-26 14:06 ` vikas gupta
2005-09-26 14:34 ` Sébastien Dugué
2005-09-27 7:09 ` vikas gupta
2005-09-28 7:25 ` Sébastien Dugué
2005-09-28 12:57 ` vikas gupta
2005-09-28 12:58 ` vikas gupta
2005-09-28 13:35 ` Sébastien Dugué
2005-09-28 14:04 ` vikas gupta
2005-09-29 9:31 ` Sébastien Dugué
2005-09-30 3:07 ` vikas gupta
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=1127725191.2069.17.camel@frecb000686 \
--to=sebastien.dugue@bull.net \
--cc=bcrl@kvack.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vikas_gupta51013@yahoo.co.in \
/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