[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [PATCH v8 1/2] virtio-crypto: Add virtio crypto device specification
On 02/09/2016, 16:05, "Alexander Graf" <firstname.lastname@example.org> wrote: >>>There is a big problem that the control handle logic is synchronization, >>>but the data queue >>>handling logic is asynchronization. We can't combine them into one >>>queue. >>>It will decrease the performance because you need indentify each packet >>>if we do this forcedly. >>Are you saying that control and data operations are handled by separate >>"blocksİ÷? >>If you combined control and data queues, there would have to be a (SW) >>demultiplexer >>that would add overhead (and potentially decrease throughout) especially >>for the data >>operations? > >Uh, the multiplexer is as simple as a switch() statement on the opcode, >no? You are assuming the backend will (always) be implemented in software. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.