On 09/26/2012 03:51 PM, Kevin Wolf wrote:
> Am 26.09.2012 01:22, schrieb ching:
>> On 09/25/2012 09:33 PM, Kevin Wolf wrote:
>>> Am 25.09.2012 00:40, schrieb ching:
On 09/24/2012 08:30 PM, Kevin Wolf wrote:
> Am 24.09.2012 13:32, schrieb ching:
>> Hi all,
>>
>> My host is qemu-
Am 26.09.2012 01:22, schrieb ching:
> On 09/25/2012 09:33 PM, Kevin Wolf wrote:
>> Am 25.09.2012 00:40, schrieb ching:
>>> On 09/24/2012 08:30 PM, Kevin Wolf wrote:
Am 24.09.2012 13:32, schrieb ching:
> Hi all,
>
> My host is qemu-1.1.1 and x64 kernel 3.5.4. The guest is using
>>>
On 09/25/2012 09:33 PM, Kevin Wolf wrote:
> Am 25.09.2012 00:40, schrieb ching:
>> On 09/24/2012 08:30 PM, Kevin Wolf wrote:
>>> Am 24.09.2012 13:32, schrieb ching:
Hi all,
My host is qemu-1.1.1 and x64 kernel 3.5.4. The guest is using aio="native"
I am trying to use unsafe
Am 25.09.2012 00:40, schrieb ching:
> On 09/24/2012 08:30 PM, Kevin Wolf wrote:
>> Am 24.09.2012 13:32, schrieb ching:
>>> Hi all,
>>>
>>> My host is qemu-1.1.1 and x64 kernel 3.5.4. The guest is using aio="native"
>>>
>>> I am trying to use unsafe cache mode to boost i/o performance.
>> aio=native
On 09/24/2012 08:30 PM, Kevin Wolf wrote:
> Am 24.09.2012 13:32, schrieb ching:
>> Hi all,
>>
>> My host is qemu-1.1.1 and x64 kernel 3.5.4. The guest is using aio="native"
>>
>> I am trying to use unsafe cache mode to boost i/o performance.
> aio=native requires the image to be opened with O_DIREC
Am 24.09.2012 13:32, schrieb ching:
> Hi all,
>
> My host is qemu-1.1.1 and x64 kernel 3.5.4. The guest is using aio="native"
>
> I am trying to use unsafe cache mode to boost i/o performance.
aio=native requires the image to be opened with O_DIRECT, i.e.
cache=none or cache=directsync. If you s
Hi all,
My host is qemu-1.1.1 and x64 kernel 3.5.4. The guest is using aio="native"
I am trying to use unsafe cache mode to boost i/o performance.
After googling a while, there are some old web page telling that linux native
aio do not use host cache.
(http://stackoverflow.com/questions/566410