From: Halil Pasic <pasic@linux.vnet.ibm.com>
To: "Longpeng (Mike)" <longpeng2@huawei.com>
Cc: qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org,
luonengjun@huawei.com, mst@redhat.com, cornelia.huck@de.ibm.com,
stefanha@redhat.com, denglingli@chinamobile.com,
Jani.Kokkonen@huawei.com, Ola.Liljedahl@arm.com,
Varun.Sethi@freescale.com, xin.zeng@intel.com,
brian.a.keating@intel.com, liang.j.ma@intel.com,
john.griffin@intel.com, weidong.huang@huawei.com, agraf@suse.de,
jasowang@redhat.com, vincent.jardin@6wind.com,
arei.gonglei@huawei.com, wangxinxin.wang@huawei.com,
jianjay.zhou@huawei.com
Subject: [virtio-dev] Re: [Qemu-devel] [v22 1/2] virtio-crypto: Add virtio crypto device specification
Date: Mon, 11 Dec 2017 14:54:25 +0100 [thread overview]
Message-ID: <2b7048c1-e2f8-ab40-c4df-afe5efd8f95d@linux.vnet.ibm.com> (raw)
In-Reply-To: <5A2E8067.4050000@huawei.com>
On 12/11/2017 01:56 PM, Longpeng (Mike) wrote:
>
>
> On 2017/12/6 19:01, Halil Pasic wrote:
>
>>
>>
>> On 12/06/2017 08:37 AM, Longpeng(Mike) wrote:
>>> +\field{outcome_len} is the size of struct virtio_crypto_session_input or
>>> +ZERO for the session-destroy operation.
>>
>> This ain't correct. It should have been something like virtio_crypto_destroy_session_input.
>>
>
> Hi Halil,
>
> I already fixed this just now.
> Do you have any other comments on v22 ? I'll send v23 tomorrow if no. :)
>
Did not read the rest of the document. I'm not in the middle of something,
but I wanted to read the operation part these days. I guess, you prefer
sending out v23 over waiting, so I guess I will wait for v23 then.
Some general questions/remarks before you spin v23:
* I'm not convinced about this 'header' and 'extra parameters' terminology.
Please see https://en.wikipedia.org/wiki/Header_(computing) for header.
I don't think it's fitting for the _flf structs.
Same about the 'extra'. Please see https://www.merriam-webster.com/dictionary/extra
(a : more than is due, usual, or necessary : additional) the things in
_vlf aren't extra at all. Do you intend to stick with is terminology?
If yes why? Please explain how should I read/understand it so that it makes
sense!
* Do we want/need to specify any alignment requirement for the
stuff in guest storage (for instance the _flf fields) or be explicit
about no alignment should be assumed (e.g virtio_crypto_mac_create_session_flf.algo
ain't necessarily aligned (in guest memory) as required by uint32_t)?
* I assume one request is supposed to correspond to one descriptor chain.
Right? If yes, could you tell me, where is this expressed in the spec.
Halil
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2017-12-11 13:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 7:37 [virtio-dev] [v22 0/2] virtio-crypto: virtio crypto device specification Longpeng(Mike)
[not found] ` <1512545840-10256-2-git-send-email-longpeng2@huawei.com>
2017-12-06 11:01 ` [virtio-dev] Re: [Qemu-devel] [v22 1/2] virtio-crypto: Add " Halil Pasic
2017-12-07 7:59 ` [virtio-dev] " Gonglei (Arei)
[not found] ` <5A2E8067.4050000@huawei.com>
2017-12-11 13:54 ` Halil Pasic [this message]
2017-12-11 14:09 ` [virtio-dev] " Michael S. Tsirkin
2017-12-11 15:41 ` Halil Pasic
[not found] ` <5A377F94.5000504@huawei.com>
2017-12-18 12:29 ` [virtio-dev] Re: [Qemu-devel] [virtio-dev] " Halil Pasic
2017-12-18 13:51 ` Michael S. Tsirkin
2017-12-18 15:27 ` Halil Pasic
2017-12-20 16:44 ` [virtio-dev] Re: [Qemu-devel] " Halil Pasic
2017-12-30 7:57 ` Longpeng (Mike)
2018-01-03 20:43 ` [virtio-dev] " Halil Pasic
2018-01-04 8:55 ` 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=2b7048c1-e2f8-ab40-c4df-afe5efd8f95d@linux.vnet.ibm.com \
--to=pasic@linux.vnet.ibm.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=cornelia.huck@de.ibm.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=longpeng2@huawei.com \
--cc=luonengjun@huawei.com \
--cc=mst@redhat.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