Hi Matthias...
On Wed, Feb 8, 2012 at 17:59, Matthias Brugger
wrote:
> If I understand the patch which introduces the blk tracer to ftrace
> (http://lwn.net/Articles/315508/) just uses the blktrace interface. So I
> wonder why using this influences the I/O behaviour.
Then I am completely clueles
Hi,
On 02/03/2012 06:59 AM, Mulyadi Santosa wrote:
>
> I could only offer this explanation:
> blktrace traces events in block level. In this level, I/O is likely
> serializedunless you have more than one physical disks.
>
> in ftrace, you see events right before it hits block level operation.
Hi :)
On Fri, Feb 3, 2012 at 02:06, Matthias Brugger
wrote:
>
> qemu -hda scheduler.raw -drive
> file=/mnt/disk/testdisk2.img,if=virtio,cache=none -m 1024 -enable-kvm -k es
> -smp 2 -vnc 127.0.0.1:10 -smb /home/matthias/nfs/
>
>
> I use qemu-0.15.1 configured with the following parameter:
>
> ./c
On 02/02/2012 07:15 PM, Mulyadi Santosa wrote:
> On Thu, Feb 2, 2012 at 17:20, Matthias Brugger
> wrote:
>> Hi all,
>>
>> I'm trying to analize I/O behavior of Qemu on the host.
>
> what is your complete command to invoke Qemu?
qemu -hda scheduler.raw -drive
file=/mnt/disk/testdisk2.img,if=virt
On Thu, Feb 2, 2012 at 17:20, Matthias Brugger
wrote:
> Hi all,
>
> I'm trying to analize I/O behavior of Qemu on the host.
what is your complete command to invoke Qemu?
sometimes Qemu's I/O behaviour can be modified by certain parameter.
All I know recent Qemu release (>= 1.x) use iothread by d
Hi all,
I'm trying to analize I/O behavior of Qemu on the host.
I used blktrace and the blk tracer for ftrace but I see different I/O
behavior.
I use 4 threads in the VM each reading sequentially a file. Readahead is
turned off. With blktrace reads are transmitted in a sequential way,
which me
