From: "Longpeng (Mike)" <longpeng2@huawei.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: virtio-dev@lists.oasis-open.org, Ola.Liljedahl@arm.com,
brian.a.keating@intel.com, wangxinxin.wang@huawei.com,
mst@redhat.com, xin.zeng@intel.com, jasowang@redhat.com,
Cornelia Huck <cohuck@redhat.com>,
luonengjun@huawei.com, qemu-devel@nongnu.org,
john.griffin@intel.com, agraf@suse.de, arei.gonglei@huawei.com,
liang.j.ma@intel.com, stefanha@redhat.com,
jianjay.zhou@huawei.com, Varun.Sethi@freescale.com,
Jani.Kokkonen@huawei.com, vincent.jardin@6wind.com,
denglingli@chinamobile.com, weidong.huang@huawei.com
Subject: Re: [Qemu-devel] [virtio-dev] Re: [v22 1/2] virtio-crypto: Add virtio crypto device specification
Date: Thu, 4 Jan 2018 16:55:32 +0800 [thread overview]
Message-ID: <5A4DEC04.7040705@huawei.com> (raw)
In-Reply-To: <41e46c1a-025f-7d03-50ac-c29e008fb9d8@linux.vnet.ibm.com>
On 2018/1/4 4:43, Halil Pasic wrote:
>
>
> On 12/30/2017 08:57 AM, Longpeng (Mike) wrote:
>>> What you actually do is the following. You define a
>>> 'VIRTIO_CRYPTO_F_<SERVICE_NAME>_STATELESS_MODE feature bit is negotiated'
>>> (A) mode and a '... bit is not negotiated (B)' mode for each service.
>>
>>> In
>>> mode A the driver has to use type A sateful requests (to which you refer
>>> as session mode). In mode B however the driver can use both stateless
>>> requests (to which you refer as stateless mode) and B type stateful
>>> requests (to which you also refer as session mode).
>> Sorry, I think the driver can use both in mode A and has to use stateful mode in
>> mode B.
>>
>
> You are right I've mixed up A and B. I think you got my point despite
> of this slip up.
>
> I'm on holiday this week. Will try to review v23 next week.
>
OK. Hoping you have a good holiday :)
> Regards,
> Halil
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
>
>
> .
>
--
Regards,
Longpeng(Mike)
next prev parent reply other threads:[~2018-01-04 8:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 7:37 [Qemu-devel] [v22 0/2] virtio-crypto: virtio crypto device specification Longpeng(Mike)
2017-12-06 7:37 ` [Qemu-devel] [v22 1/2] virtio-crypto: Add " Longpeng(Mike)
2017-12-06 11:01 ` Halil Pasic
2017-12-07 7:59 ` Gonglei (Arei)
2017-12-11 12:56 ` Longpeng (Mike)
2017-12-11 13:54 ` Halil Pasic
2017-12-11 14:09 ` Michael S. Tsirkin
2017-12-11 15:41 ` Halil Pasic
2017-12-18 8:43 ` [Qemu-devel] [virtio-dev] " Longpeng (Mike)
2017-12-18 12:29 ` Halil Pasic
2017-12-18 13:51 ` Michael S. Tsirkin
2017-12-18 15:27 ` Halil Pasic
2017-12-23 9:11 ` [Qemu-devel] [virtio-dev] " Longpeng (Mike)
2017-12-20 16:44 ` [Qemu-devel] " Halil Pasic
2017-12-30 7:57 ` Longpeng (Mike)
2018-01-03 20:43 ` Halil Pasic
2018-01-04 8:55 ` Longpeng (Mike) [this message]
2017-12-06 7:37 ` [Qemu-devel] [v22 2/2] virtio-crypto: Add conformance clauses Longpeng(Mike)
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=5A4DEC04.7040705@huawei.com \
--to=longpeng2@huawei.com \
--cc=Jani.Kokkonen@huawei.com \
--cc=Ola.Liljedahl@arm.com \
--cc=Varun.Sethi@freescale.com \
--cc=agraf@suse.de \
--cc=arei.gonglei@huawei.com \
--cc=brian.a.keating@intel.com \
--cc=cohuck@redhat.com \
--cc=denglingli@chinamobile.com \
--cc=jasowang@redhat.com \
--cc=jianjay.zhou@huawei.com \
--cc=john.griffin@intel.com \
--cc=liang.j.ma@intel.com \
--cc=luonengjun@huawei.com \
--cc=mst@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vincent.jardin@6wind.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=wangxinxin.wang@huawei.com \
--cc=weidong.huang@huawei.com \
--cc=xin.zeng@intel.com \
/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).