From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: jgg@ziepe.ca, linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, philip.b.tricca@intel.com,
James.Bottomley@HansenPartnership.com, "Dock,
Deneen T" <deneen.t.dock@intel.com>
Subject: Re: [PATCH v3 0/2] tpm: add support for nonblocking operation
Date: Thu, 21 Jun 2018 10:36:20 -0700 [thread overview]
Message-ID: <fff9a2ae-6f18-2401-f65b-d53f1506bbdf@intel.com> (raw)
In-Reply-To: <20180621171746.GJ11859@linux.intel.com>
On 06/21/2018 10:17 AM, Jarkko Sakkinen wrote:
> On Tue, Jun 19, 2018 at 05:45:35PM -0700, Tadeusz Struk wrote:
>> 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-tss
>
> I 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
WARNING: multiple messages have this Message-ID (diff)
From: tadeusz.struk@intel.com (Tadeusz Struk)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v3 0/2] tpm: add support for nonblocking operation
Date: Thu, 21 Jun 2018 10:36:20 -0700 [thread overview]
Message-ID: <fff9a2ae-6f18-2401-f65b-d53f1506bbdf@intel.com> (raw)
In-Reply-To: <20180621171746.GJ11859@linux.intel.com>
On 06/21/2018 10:17 AM, Jarkko Sakkinen wrote:
> On Tue, Jun 19, 2018 at 05:45:35PM -0700, Tadeusz Struk wrote:
>> 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-tss
>
> I 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
next prev parent reply other threads:[~2018-06-21 17:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 17:58 [PATCH v3 0/2] tpm: add support for nonblocking operation Tadeusz Struk
2018-06-12 17:58 ` Tadeusz Struk
2018-06-12 17:58 ` [PATCH v3 1/2] tpm: add ptr to the tpm_space struct to file_priv Tadeusz Struk
2018-06-12 17:58 ` Tadeusz Struk
2018-06-12 17:58 ` [PATCH v3 2/2] tpm: add support for nonblocking operation Tadeusz Struk
2018-06-12 17:58 ` Tadeusz Struk
2018-06-13 17:55 ` J Freyensee
2018-06-13 17:55 ` J Freyensee
2018-06-13 17:55 ` J Freyensee
2018-06-13 18:05 ` Tadeusz Struk
2018-06-13 18:05 ` Tadeusz Struk
2018-06-13 18:05 ` Tadeusz Struk
2018-06-19 13:10 ` [PATCH v3 0/2] " Jarkko Sakkinen
2018-06-19 13:10 ` Jarkko Sakkinen
2018-06-20 0:45 ` Tadeusz Struk
2018-06-20 0:45 ` Tadeusz Struk
2018-06-20 23:59 ` James Bottomley
2018-06-20 23:59 ` James Bottomley
2018-06-21 1:24 ` Tadeusz Struk
2018-06-21 1:24 ` Tadeusz Struk
2018-06-21 5:26 ` James Bottomley
2018-06-21 5:26 ` James Bottomley
2018-06-21 5:26 ` James Bottomley
2018-06-21 16:20 ` Tadeusz Struk
2018-06-21 16:20 ` Tadeusz Struk
2018-06-21 17:17 ` Jarkko Sakkinen
2018-06-21 17:17 ` Jarkko Sakkinen
2018-06-21 17:36 ` Tadeusz Struk [this message]
2018-06-21 17:36 ` Tadeusz Struk
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=fff9a2ae-6f18-2401-f65b-d53f1506bbdf@intel.com \
--to=tadeusz.struk@intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=deneen.t.dock@intel.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=philip.b.tricca@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.