search for: eassili

On 5/29/19 10:13 PM, Eric Blake wrote: > Benchmark-wise, using the same setup as in commit e897ed70, I see > an order-of-magnitude slowdown: > > Pre-patch, the runs averaged 1.266s, 1.30E+08 bits/s > Post-patch, the runs averaged 11.663s, 1.41E+07 bits/s > > This will need further profiling to determine how much is nbdkit's > fault, and how much is libnbd's. I

Sorry for the noise if this isn't the appropriate venue for this. I posted this last month to xen-devel: http://lists.xensource.com/archives/html/xen-devel/2007-11/msg00777.html I can reliably cause a paravirt_ops Xen guest to hang during intensive IO. My current recipe is an untar/tar loop, without compression, of a kernel tree. For example: wget

Sorry for the noise if this isn't the appropriate venue for this. I posted this last month to xen-devel: http://lists.xensource.com/archives/html/xen-devel/2007-11/msg00777.html I can reliably cause a paravirt_ops Xen guest to hang during intensive IO. My current recipe is an untar/tar loop, without compression, of a kernel tree. For example: wget

Sorry for the noise if this isn't the appropriate venue for this. I posted this last month to xen-devel: http://lists.xensource.com/archives/html/xen-devel/2007-11/msg00777.html I can reliably cause a paravirt_ops Xen guest to hang during intensive IO. My current recipe is an untar/tar loop, without compression, of a kernel tree. For example: wget

On Thu, May 30, 2019 at 02:00:48PM -0500, Eric Blake wrote: > [...] which is more eassily explained by the > serialization nature that libnbd is never read()ing from one thread at > the same time another thread is write()ing. > > [...] libnbd > works around that by using non-blocking sockets and prioritizing reads > over writes rather than insisting on complete transactions).

Patch 1 played with an early draft of Rich's Fedora 30 libnbd package: https://bugzilla.redhat.com/show_bug.cgi?id=1713767#c17 Note that comment 21 provides a newer package 0.1.1-1 with a different API; and that libnbd has more unreleased API changes in the pipeline (whether that will be called 0.2 or 0.1.2); so we'll have to tweak things based on what is actually available in distros.