@Stephane,
did upstream ever accept your patch?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/595117
Title:
qemu-nbd slow and missing writeback cache option
Status in QEMU:
Invalid
Status in
For the record, there's more on that bug at
http://thread.gmane.org/gmane.linux.ubuntu.bugs.server/36923
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/595117
Title:
qemu-nbd slow and missing
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
2010-06-24 00:16:03 -, Jamie Lokier:
Serge Hallyn wrote:
The default of qemu-img (of using O_SYNC) is not very sensible
because anyway, the client (the kernel) uses caches (write-back),
(and qemu-nbd -d doesn't flush those by the way). So if for
instance qemu-nbd is killed, regardless
On Thu, Jun 24, 2010 at 01:16:03AM +0100, Jamie Lokier wrote:
Serge Hallyn wrote:
The default of qemu-img (of using O_SYNC) is not very sensible
because anyway, the client (the kernel) uses caches (write-back),
(and qemu-nbd -d doesn't flush those by the way). So if for
instance qemu-nbd
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Confirmed
--
qemu-nbd slow and missing writeback cache option
https://bugs.launchpad.net/bugs/595117
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Invalid
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = Incomplete
--
qemu-nbd slow and missing writeback cache option
https://bugs.launchpad.net/bugs/595117
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Invalid
Serge Hallyn wrote:
The default of qemu-img (of using O_SYNC) is not very sensible
because anyway, the client (the kernel) uses caches (write-back),
(and qemu-nbd -d doesn't flush those by the way). So if for
instance qemu-nbd is killed, regardless of whether qemu-nbd uses
O_SYNC, O_DIRECT or
** Tags added: patch
--
qemu-nbd slow and missing writeback cache option
https://bugs.launchpad.net/bugs/595117
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Invalid
Status in “qemu-kvm” package in Ubuntu: Incomplete
** Also affects: qemu
Importance: Undecided
Status: New
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
qemu-nbd slow and missing writeback cache option
https://bugs.launchpad.net/bugs/595117
You received this bug notification because you are a member of qemu-
Noone has confirmed, but have passed along to upstream. If upstream
takes this patch then we will likely pull it into our patchset.
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = Incomplete
--
qemu-nbd slow and missing writeback cache option
https://bugs.launchpad.net/bugs/595117
Patches should go to qemu-devel, not bug reports.
** Changed in: qemu
Status: New = Invalid
--
qemu-nbd slow and missing writeback cache option
https://bugs.launchpad.net/bugs/595117
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
Stephane-
Could you please send that patch to the qemu-devel@ mailing list?
Thanks!
--
qemu-nbd slow and missing writeback cache option
https://bugs.launchpad.net/bugs/595117
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in
13 matches
Mail list logo