[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Do we need CONFIG_AIO?
From: |
Todd T. Fries |
Subject: |
Re: [Qemu-devel] Do we need CONFIG_AIO? |
Date: |
Mon, 25 May 2009 10:24:47 -0500 |
User-agent: |
Mutt/1.5.19 (2009-01-05) |
Penned by Avi Kivity on 20090525 16:47.14, we have:
> Todd T. Fries wrote:
>> Penned by Stefano Stabellini on 20090525 12:49.08, we have:
>> | Christoph Hellwig wrote:
>> | | > Currently all aio code in the raw-posix block driver depends on a
>> | > CONFIG_AIO symbol that gets set based on the availability of the
>> | > pthreads library. Beeing able to rely on unconditional aio support
>> | > means we could remove the whole code for plain bdrv_read/bdrv_write
>> | > in raw-posix.c which is about 300 lines of code and a duplicated code
>> | > path. Is there any Posix-ish platform qemu supports that does not
>> | > have pthreads support?
>> | > | | MiniOS.
>> | I would appreciate if you keep that flag.
>>
>> You seem to be under the illusion that pthreads implies AIO.
>>
>
> He isn't.
>
>> OpenBSD has two flavors of threads libraries (arguably one is not
>> fit for consumption yet) and neither provide AIO.
>>
>> This flag is most useful for OpenBSD as well.
>>
>
> Qemu's CONFIG_AIO requires thread support from the host, not posix aio
> support.
If thats the way things work, great. I just recall when AIO made its debut
in qemu we had to figure out some strange workarounds..
--
Todd Fries .. address@hidden
_____________________________________________
| \ 1.636.410.0632 (voice)
| Free Daemon Consulting, LLC \ 1.405.227.9094 (voice)
| http://FreeDaemonConsulting.com \ 1.866.792.3418 (FAX)
| "..in support of free software solutions." \ 250797 (FWD)
| \
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A
http://todd.fries.net/pgp.txt
Re: [Qemu-devel] Do we need CONFIG_AIO?, Anthony Liguori, 2009/05/26