From: Rik van Riel <riel@redhat.com>
To: Christian.Limpach@cl.cam.ac.uk
Cc: xen-devel@lists.xensource.com
Subject: Re: RFC/PATCH: hdparm tunable IDE write cache for HVM
Date: Fri, 11 Aug 2006 13:44:51 -0400 [thread overview]
Message-ID: <44DCC213.90607@redhat.com> (raw)
In-Reply-To: <3d8eece20608110407s6c306d02h884dfb700cedd912@mail.gmail.com>
Christian Limpach wrote:
> On 8/11/06, Rik van Riel <riel@redhat.com> wrote:
>> qemu 0.8.2 has a flush callback to the storage backends, so now it is
>> possible to implement hdparm tunable IDE write cache enable/disable for
>> guest domains, allowing people to pick speed or data consistency on a
>> case by case basis.
>>
>> As an added benefit, really large LBA48 IOs will now no longer be broken
>> up into smaller IOs on the host side.
>>
>> What do you think?
>
> Looks good, are you confident that you have identified all the places
> where a flush is needed?
Yes, bdrv_write() is only called from 2 places in ide.c, and
both of them have a bdrv_flush() call now.
> Doesn't qemu do flushes in the first place
> and wouldn't it then have the same issues?
Nope, qemu does not seem to do any flushes by itself...
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
next prev parent reply other threads:[~2006-08-11 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 6:28 RFC/PATCH: hdparm tunable IDE write cache for HVM Rik van Riel
2006-08-11 11:07 ` Christian Limpach
2006-08-11 17:44 ` Rik van Riel [this message]
2006-08-20 23:03 ` Christian Limpach
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=44DCC213.90607@redhat.com \
--to=riel@redhat.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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.