From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47479) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wwrr1-0000C2-7s for qemu-devel@nongnu.org; Tue, 17 Jun 2014 07:47:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wwrqt-0007WL-Cd for qemu-devel@nongnu.org; Tue, 17 Jun 2014 07:47:06 -0400 Received: from mx1.redhat.com ([209.132.183.28]:30096) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wwrqt-0007WF-4E for qemu-devel@nongnu.org; Tue, 17 Jun 2014 07:46:59 -0400 Message-ID: <53A02AA6.2060006@redhat.com> Date: Tue, 17 Jun 2014 13:46:46 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1401889659-24035-1-git-send-email-pl@kamp.de> <53903469.8070902@msgid.tls.msk.ru> <539FDCAD.5060006@kamp.de> <53A02351.8060900@redhat.com> <53A02867.7090400@kamp.de> In-Reply-To: <53A02867.7090400@kamp.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] block/iscsi: use 16 byte CDBs only when necessary List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven , Michael Tokarev , ronnie sahlberg Cc: Kevin Wolf , qemu-devel , Stefan Hajnoczi Il 17/06/2014 13:37, Peter Lieven ha scritto: > On 17.06.2014 13:15, Paolo Bonzini wrote: >> Il 17/06/2014 08:14, Peter Lieven ha scritto: >>>> >>> >>> BTW, while debugging a case with a bigger storage supplier I found >>> that open-iscsi seems to do exactly this undeterministic behaviour. >>> I have a 3TB LUN. If I access < 2TB sectors it uses READ10/WRITE10 and >>> if I go beyond 2TB it changes to READ16/WRITE16. >> >> Isn't that exactly what your latest patch does for >64K sector writes? :) > > Not exactly, we choose the default by checking the LUN size. 10 Byte for > < 2TB and 16 Byte otherwise. Yeah, I meant introducing the non-determinism. > My latest patch makes an exception if a request is bigger than 64K > sectors and > switches to 16 Byte requests. These would otherwise end in an I/O error. It could also be split at the block layer, like we do for unmap. I think there's also a maximum transfer size somewhere in the VPD, we could to READ16/WRITE16 if it is >64K sectors. Paolo