linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Nicholas A. Bellinger" <nab@daterainc.com>,
	target-devel <target-devel@vger.kernel.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	kvm-devel <kvm@vger.kernel.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
	Sagi Grimberg <sagig@mellanox.com>,
	Nicholas Bellinger <nab@linux-iscsi.org>
Subject: Re: [RFC 0/6] vhost/scsi: Add T10 PI SGL passthrough support
Date: Mon, 24 Feb 2014 11:23:43 +0100	[thread overview]
Message-ID: <530B1DAF.7010702@redhat.com> (raw)
In-Reply-To: <1393219950-18613-1-git-send-email-nab@daterainc.com>

Il 24/02/2014 06:32, Nicholas A. Bellinger ha scritto:
> AFAICT up until this point the ->prio field has been unused, but
> I'm certainly open to better ways of signaling (to vhost) that some
> number of metadata iovs are to be expected..  Any thoughts..?

Hi nab,

the virtio-scsi side of the patch is nice and readable.  As requested, 
here are my thoughts on how to add it to the standard.

The ->prio field is there to mimic SAM's command priority field (8.7 in 
my copy of the standard).  I'd rather leave it alone; I understand this 
is the main reason why this patch is RFC.

Since we have a new feature bit, we can add a new element before the 
cdb.  It could be a count of scatter/gather list like you did here, or 
it could be a byte count.  Even better, we can add _two_ new fields, one 
for protection data out and one for protection data in.

Also, do we need an equivalent of the residual field, but for metadata?

Finally, any reason why you put the data sg elements before the metadata 
sg elements?  I would have thought that processing is a bit simpler if 
either the metadata comes first, or you store in the command header the 
data count (either sg or byte).  Because the virtio buffers form a 
linked list, it's a bit backwards to put metadata last, and store 
metadata count in the command header; it prevents you from processing 
the buffers online because you don't know when the metadata starts. 
Even though the Linux virtio layer always gives you a buffer count, this 
need not be the case in general.

Paolo

  parent reply	other threads:[~2014-02-24 10:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24  5:32 [RFC 0/6] vhost/scsi: Add T10 PI SGL passthrough support Nicholas A. Bellinger
2014-02-24  5:32 ` [RFC 1/6] vhost/scsi: Move sanity check into vhost_scsi_map_iov_to_sgl Nicholas A. Bellinger
2014-02-24  5:32 ` [RFC 2/6] vhost/scsi: Add preallocation of protection SGLs Nicholas A. Bellinger
2014-02-24  5:32 ` [RFC 3/6] vhost/scsi: Add T10 PI IOV -> SGL memory mapping logic Nicholas A. Bellinger
2014-02-24  5:32 ` [RFC 4/6] vhost/scsi: Enable T10 PI IOV -> SGL memory mapping Nicholas A. Bellinger
2014-02-24  5:32 ` [RFC 5/6] vhost/scsi: Add new VIRTIO_SCSI_F_T10_PI feature bit Nicholas A. Bellinger
2014-02-24  5:32 ` [RFC 6/6] virtio-scsi: Enable DIF/DIX modes in SCSI host LLD Nicholas A. Bellinger
2014-02-24  9:10 ` [RFC 0/6] vhost/scsi: Add T10 PI SGL passthrough support Michael S. Tsirkin
2014-02-24 10:23 ` Paolo Bonzini [this message]
2014-02-25  6:05   ` Nicholas A. Bellinger
2014-02-26  1:20     ` Martin K. Petersen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=530B1DAF.7010702@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mst@redhat.com \
    --cc=nab@daterainc.com \
    --cc=nab@linux-iscsi.org \
    --cc=sagig@mellanox.com \
    --cc=target-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).