[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Do we need CONFIG_AIO?
From: |
Stefano Stabellini |
Subject: |
Re: [Qemu-devel] Do we need CONFIG_AIO? |
Date: |
Tue, 26 May 2009 11:02:25 +0100 |
User-agent: |
Thunderbird 2.0.0.14 (X11/20080505) |
Anthony Liguori wrote:
> Stefano Stabellini wrote:
>> 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.
>>
>
> Threads are not going to be able to remain an optional dependency
> forever. I would be willing to merge something to remove CONFIG_AIO
> although I expect that there will be some fall out. Some people are
> using --disable-aio today for either historic reasons or because there
> are weird bugs with AIO enabled.
>
Obviously I would prefer if threads remained optional too, but let's
just focus on AIO for the moment: as Todd pointed out OpenBSD doesn't
currently provide AIO and also some small libc, like newlib, do not have
AIO either.
- Re: [Qemu-devel] Do we need CONFIG_AIO?, (continued)
Re: [Qemu-devel] Do we need CONFIG_AIO?, Todd T. Fries, 2009/05/25
Re: [Qemu-devel] Do we need CONFIG_AIO?, Anthony Liguori, 2009/05/26