[PATCH v3 0/2] tpm: add support for nonblocking operation
From: Tadeusz Struk <hidden>
Date: 2018-06-21 17:36:34
Also in:
linux-integrity, lkml
On 06/21/2018 10:17 AM, Jarkko Sakkinen wrote:
On Tue, Jun 19, 2018 at 05:45:35PM -0700, Tadeusz Struk wrote:quoted
Hi Jarkko, Thanks for reviewing the patch. There are applications/frameworks where a worker thread is not an option. Take for example the IoT use-cases and frameworks like IoT.js, or "Node.js for IoT". They are all single threaded, event-driven frameworks, using non-blocking I/O as the base of their processing model. Similarly embedded applications, which are basically just a single threaded event loop, quite often don't use threads because of resources constrains. If your concern is that user space will not adopt to this, I can say that TSS library [1] is currently blocked on this feature, and we can not enable some of the use-cases mentioned above because of this. Thanks, Tadeusz [1] https://github.com/tpm2-software/tpm2-tssI put this into "mathematical" terms. TPM is by nature is blocking. It does not scale this way so you are essentially just simulating non-blocking behaviour.
That is correct, and this is exactly why we need this. Thanks, -- Tadeusz -- To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to majordomo at vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html