All of lore.kernel.org
 help / color / mirror / Atom feed
From: cauchy-love  <cauchy-love@163.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Greate difference of disk I/O performance for guest on Qemu-2.30 of CentOS.
Date: Wed, 24 Jun 2015 20:31:54 +0800 (CST)	[thread overview]
Message-ID: <79939a29.26a14.14e258d9cd6.Coremail.cauchy-love@163.com> (raw)
In-Reply-To: <558AA072.3080507@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]

Hi, Paolo,


   Sorry, but I don't know what does bisect mean exactly. Could you please explain it? I feel it might be some kernel configuration items introduce this problem. I am also trying other kernel versions from 2.6.34 to 2.6.38 (2.6.33.3 has good performance like 2.6.32) and will show you the results.


Thanks,


Yi








At 2015-06-24 20:20:02, "Paolo Bonzini" <pbonzini@redhat.com> wrote:
>
>
>On 24/06/2015 14:14, cauchy-love wrote:
>>     I have updated the kernel of CentOS 6.5 from 2.6.32 to higher
>> versions (2.6.39+) and found the disk IO write performance of my guest
>> OS degraded significantly (around 1/10 of 2.6.32) while read performance
>> was not influenced. That means everything is the same (i.e., hardware
>> configurations, BIOS, filesystems (ext4)) except the kernel. I would be
>> greatly apprieciated if you can provide some help about debugging this
>> problem. I have tried to trace the qemu but didn't get any progress.
>
>Can you bisect it further between 2.6.32 and 2.6.39?
>
>Stefan, does it ring any bell?
>
>Paolo

[-- Attachment #2: Type: text/html, Size: 2072 bytes --]

  parent reply	other threads:[~2015-06-24 12:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 13:14 [Qemu-devel] Greate difference of disk I/O performance for guest on Qemu-2.30 of CentOS cauchy-love
2015-06-16 13:05 ` Stefan Hajnoczi
2015-06-19  0:40   ` cauchy-love
2015-06-19 15:24     ` Stefan Hajnoczi
2015-06-19  1:03   ` cauchy-love
2015-06-19  8:37     ` Paolo Bonzini
2015-06-23  3:22       ` cauchy-love
     [not found]       ` <5ec70e6c.267de.14e257e00ab.Coremail.cauchy-love@163.com>
     [not found]         ` <558AA072.3080507@redhat.com>
2015-06-24 12:31           ` cauchy-love [this message]
2015-06-24 12:32             ` Paolo Bonzini
2015-06-24 12:50               ` cauchy-love

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=79939a29.26a14.14e258d9cd6.Coremail.cauchy-love@163.com \
    --to=cauchy-love@163.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.