From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Paul Schlacter <wlfightup@gmail.com>, stefanha@redhat.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu disk use writeback don't take effect in centos 7.2 1511
Date: Fri, 3 Nov 2017 09:10:45 +0000 [thread overview]
Message-ID: <20171103091045.GA2616@work-vm> (raw)
In-Reply-To: <CADak6y5zT2qxHe8-iCQhpgxdAyHcerMMbcDNvRig8i2PvopHBg@mail.gmail.com>
* Paul Schlacter (wlfightup@gmail.com) wrote:
> latest progress:
> use centos 7.2 https://cloud.centos.org/centos/7/images/
> test version: 1511 1601 1604 1606 1608
>
> From the above version in turn test, found the previous version 1511 1601
> 1603 have the problem,
> The latter two versions 1606 1608 are normal, dont't have the prblem,
> Normal is cache = writeback io significantly higher than none mode
>
> why?
It's a fun bug, but I don't know the cause - the fact it's dependent
on guest version but fixed, suggests something changed in the guest
kernel. If you really wanted to figure out why I guess the only way
would be to walk through the CentOS guest kernel versions and find the
exact kernel that fixed it; then we could hunt down which change fixed
it.
(I've cc'd in Stefan for block stuff, but this is sounding more guest
than qemu)
Dave
> On Wed, Nov 1, 2017 at 8:03 PM, Paul Schlacter <wlfightup@gmail.com> wrote:
>
> > Hi David:
> > yes, with the same qemu, centos 7.2 guest cache is writeback and
> > none, the disk io almost, writeback feeling no effect.
> > but 7.1/7.3/7.4 cache is writeback was significantly faster than
> > none model
> >
> > On Wed, Nov 1, 2017 at 8:02 PM, Paul Schlacter <wlfightup@gmail.com>
> > wrote:
> >
> >> Hi David:
> >> yes, with the same qemu, centos 7.2 guest cache is writeback and
> >> none, the disk io almost, writeback feeling no effect.
> >> but 7.1/7.3/7.4 cache is writeback was significantly faster than
> >> none model
> >>
> >> On Wed, Nov 1, 2017 at 5:45 PM, Dr. David Alan Gilbert <
> >> dgilbert@redhat.com> wrote:
> >>
> >>> * Paul Schlacter (wlfightup@gmail.com) wrote:
> >>> > qemu version: 2.9.0
> >>> > image: centos 7.2 1511 raw
> >>> > cache mode: writeback
> >>> >
> >>> >
> >>> > In centos7.2 time, the use of writeback and none, the result of dd
> >>> disk is
> >>> > the same io, no change
> >>> >
> >>> > But I replaced centos7.1 centos7.3 centos7.4 when writeback was
> >>> > significantly faster than none
> >>> >
> >>> > Would like to ask what is going on, how to solve ?
> >>>
> >>> Hi Paul,
> >>> Can you just clarify your setup please; do you mean that
> >>> with the same qemu setup but a 7.2 guest rather than a 7.1/7.3 guest
> >>> the behaviour changes?
> >>>
> >>> Dave
> >>>
> >>> --
> >>> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> >>>
> >>
> >>
> >
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-11-03 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 7:44 [Qemu-devel] qemu disk use writeback don't take effect in centos 7.2 1511 Paul Schlacter
2017-11-01 9:45 ` Dr. David Alan Gilbert
[not found] ` <CADak6y485_OSHrzji4Wq7_3vOrK+ch6Vm1FW1RMidSzoO3U-kQ@mail.gmail.com>
2017-11-01 12:03 ` Paul Schlacter
2017-11-03 3:46 ` Paul Schlacter
2017-11-03 9:10 ` Dr. David Alan Gilbert [this message]
2017-11-03 10:09 ` Stefan Hajnoczi
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=20171103091045.GA2616@work-vm \
--to=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wlfightup@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).