qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: "virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Cornelia Huck" <cornelia.huck@de.ibm.com>,
	"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
	"Hanweidong (Randy)" <hanweidong@huawei.com>,
	"Jani Kokkonen" <Jani.Kokkonen@huawei.com>,
	"Zhoujian (jay, Euler)" <jianjay.zhou@huawei.com>,
	"Lingli Deng" <denglingli@chinamobile.com>,
	"Mihai Claudiu Caraman" <mike.caraman@nxp.com>,
	"'Ola Liljedahl@arm.com'" <Ola.Liljedahl@arm.com>,
	"Crasta Denis-B22176" <denis.crasta@freescale.com>,
	"Varun Sethi" <Varun.Sethi@freescale.com>,
	"'Venkatesan, Venky'" <venky.venkatesan@intel.com>,
	"Catalin Vasile" <cata.vasile@nxp.com>,
	"'François-Frédéric Ozog'" <ff.ozog@6wind.com>,
	Luonengjun <luonengjun@huawei.com>
Subject: Re: [Qemu-devel] [RFC v3] virtio-crypto specification
Date: Tue, 19 Apr 2016 17:23:21 +0300	[thread overview]
Message-ID: <20160419172014-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020B03164A0@SZXEMA503-MBS.china.huawei.com>

On Tue, Apr 19, 2016 at 08:37:13AM +0000, Gonglei (Arei) wrote:
> Hi all,
> 
> This is the specification (version 3) about a new virtio crypto device. 
> 
> Changes from v2:
>  - Reserve virtio device ID 20 for crypto device. [Cornelia]
>  - Drop all feature bits, those capabilities are offered by the device all the time.  [Stefan & Cornelia]
>  - Add a new section 1.4.2 for driver requirements. [Stefan]
>  - Use definite type definition instead of enum type in some structure. [Stefan]

In fact this is not how rest of spec does this:

\begin{lstlisting}
struct virtio_net_hdr {
#define VIRTIO_NET_HDR_F_NEEDS_CSUM    1
        u8 flags;
#define VIRTIO_NET_HDR_GSO_NONE        0
#define VIRTIO_NET_HDR_GSO_TCPV4       1
#define VIRTIO_NET_HDR_GSO_UDP         3
#define VIRTIO_NET_HDR_GSO_TCPV6       4
#define VIRTIO_NET_HDR_GSO_ECN      0x80
        u8 gso_type;
        le16 hdr_len;
        le16 gso_size;
        le16 csum_start;
        le16 csum_offset;
        le16 num_buffers;
};
\end{lstlisting}

the advantage is that field width is explicit.

-- 
MST

  reply	other threads:[~2016-04-19 14:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19  8:37 [Qemu-devel] [RFC v3] virtio-crypto specification Gonglei (Arei)
2016-04-19 14:23 ` Michael S. Tsirkin [this message]
2016-04-20  0:29   ` Gonglei (Arei)
2016-04-21 15:23 ` Stefan Hajnoczi
2016-04-22  0:28   ` Gonglei (Arei)

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=20160419172014-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=Jani.Kokkonen@huawei.com \
    --cc=Ola.Liljedahl@arm.com \
    --cc=Varun.Sethi@freescale.com \
    --cc=arei.gonglei@huawei.com \
    --cc=cata.vasile@nxp.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=denglingli@chinamobile.com \
    --cc=denis.crasta@freescale.com \
    --cc=ff.ozog@6wind.com \
    --cc=hanweidong@huawei.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=luonengjun@huawei.com \
    --cc=mike.caraman@nxp.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=venky.venkatesan@intel.com \
    --cc=virtio-dev@lists.oasis-open.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).