From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36183) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XR0ib-0007lW-Kv for qemu-devel@nongnu.org; Mon, 08 Sep 2014 11:19:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XR0iR-0004vM-GR for qemu-devel@nongnu.org; Mon, 08 Sep 2014 11:19:01 -0400 Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:34571 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XR0iR-0004vD-6P for qemu-devel@nongnu.org; Mon, 08 Sep 2014 11:18:51 -0400 Message-ID: <540DC8D7.80905@kamp.de> Date: Mon, 08 Sep 2014 17:18:47 +0200 From: Peter Lieven MIME-Version: 1.0 References: <1409935888-18552-1-git-send-email-pl@kamp.de> <1409935888-18552-3-git-send-email-pl@kamp.de> <20140908134434.GB22582@irqsave.net> <540DB3E2.6010905@redhat.com> <540DB583.4030101@kamp.de> <540DB5EB.2070705@redhat.com> <540DBEBD.9040701@kamp.de> <540DC059.4000907@redhat.com> <540DC7FB.1040804@redhat.com> In-Reply-To: <540DC7FB.1040804@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 2/4] block: immediately cancel oversized read/write requests List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , ronnie sahlberg Cc: =?UTF-8?B?QmVub8OudCBDYW5ldA==?= , Kevin Wolf , qemu-devel , Stefan Hajnoczi , Max Reitz On 08.09.2014 17:15, Paolo Bonzini wrote: > Il 08/09/2014 17:13, ronnie sahlberg ha scritto: >> What I would like to see would also be to report these limitations to >> the guest itself to prevent it from generating too large I/Os. > That's difficult because you don't want a backend change (e.g. from > local storage to iSCSI) to change the vital product data in the guest. I hadn't that in mind.... > > That's why we have splitting code for discard, and why we would have to > add it for read/write too. Why should a guest generate such big requests. Afaik the reported limit for e.g. virtio-blk is 1024 sectors (reported through blockdev --getmaxsect /dev/vda). I think it was only the multiwrite_merge code causing trouble here. Peter