On 14/06/2016 17:59, Alex Bligh wrote: > >> On 14 Jun 2016, at 16:11, Paolo Bonzini <[email protected]> wrote: >> >>> To illustrate the problem, look consider what qemu itself would do as >>> a server if it can't buffer the entire read issued to it. >> >> Return ENOMEM? > > Well OK, qemu then 'works' on the basis it breaks another > part of the spec, which is coping with long reads.
ENOMEM is a documented error code, and the limits extension will help with that as well. >> However, it looks like the >> de facto status prior to structured replies is that the error is in the >> spec, and this patch introduces a regression. > > Well, I guess the patch makes it work the same as the > reference server implementation and the spec, which I'd > consider a fix. My view is that the error is in the > kernel client. ... and QEMU and BSD. What good is a server that doesn't interoperate (albeit only in error cases) with any client? Paolo ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381 _______________________________________________ Nbd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nbd-general
