From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38175)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <apyrgio@arrikto.com>) id 1aIcYk-0006mg-8h
	for qemu-devel@nongnu.org; Mon, 11 Jan 2016 08:30:59 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <apyrgio@arrikto.com>) id 1aIcYe-0005Py-BR
	for qemu-devel@nongnu.org; Mon, 11 Jan 2016 08:30:58 -0500
Received: from mx0.arrikto.com ([212.71.252.59]:39862)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <apyrgio@arrikto.com>) id 1aIcYe-0005Mg-2L
	for qemu-devel@nongnu.org; Mon, 11 Jan 2016 08:30:52 -0500
References: <1450284917-10508-1-git-send-email-apyrgio@arrikto.com>
	<5671AA78.8050603@redhat.com> <5672768E.70101@arrikto.com>
	<56728F08.7070702@redhat.com> <5672B451.1050302@arrikto.com>
	<5672B4E6.8000504@redhat.com>
From: Alex Pyrgiotis <apyrgio@arrikto.com>
Message-ID: <5693AE88.8030500@arrikto.com>
Date: Mon, 11 Jan 2016 15:30:48 +0200
MIME-Version: 1.0
In-Reply-To: <5672B4E6.8000504@redhat.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH 0/9] Add full scatter-gather support for
 SCSI generic devices
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org

On 12/17/2015 03:13 PM, Paolo Bonzini wrote:
> 
> 
> On 17/12/2015 14:10, Alex Pyrgiotis wrote:
>>>>>> Which commands have large payloads and are on the data path, for
>>>>>> scsi-block?  Or is the use case just scsi-generic (e.g. tape devices?)?
>>
>> If I understand correctly, what you're saying is that if "scsi-block" is
>> started with "cache=writeback" and internally uses ioctl()s to bypass
>> the page cache, why not set "cache=none" beforehand and use
>> readv()/writev()?
>>
>> This is a valid suggestion, but this patch does not target only the
>> "scsi-block" device type. Its purpose is to allow faster read/writes via
>> ioctl()s, either to a "scsi-block" device or to a "scsi-generic" device.
>> Note that the latter device type can only use ioctl()s, so it cannot
>> benefit from the readv()/writev() DMA interface and currently has to use
>> a bounce buffer.
> 
> Okay, so that answers my questions; there is still a valid use case for
> e.g. tape devices, and of course for when someone forgets to use scsi-block.
> 
> Paolo

Ping?

Alex