Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp2309720imm; Thu, 21 Jun 2018 10:19:06 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLvYAn6pSY8zfYmLsR7c+TmkMcg2BPOIPbwUyqiw8050RVmhoShztp8CNcxmIvJW9ut0rX6 X-Received: by 2002:a65:5106:: with SMTP id f6-v6mr23068067pgq.122.1529601546401; Thu, 21 Jun 2018 10:19:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529601546; cv=none; d=google.com; s=arc-20160816; b=YZUNveomiwjri3q+dFHh36he71bbdi5X6x9+Efv9bMZOSb8QybJwtT7unyWTn7zq5t 6Up2GmmszV/4S0XMWQAyir2q/6bNL+9tzvPqAgtpY0Eq5oZ1kc25i4RyHIexpxnXff7L OmzoiQqgSseTlo9pI50Q4tYi34tHKDvpS/YBFZccd/ZfAL9mFBpMcPOZkoHjFLB/RA55 x8ZXKAf/vNozqpI7Cp2Z+kqbv9wFTqxrvzic1/lnxIHMflTvvBc9FMBdAoee1AbWgTUe Gu9xkwbGSTsxarg6c1CTqK0bwQyEkW/xqy8ijRQxStbYO5fLttcNQkyS++u2s+nQNlCO g5HQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:organization:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=5gv0UacQ+LvlGzN9YCU508WVGi+IjaVhFn/FsiKcY0s=; b=oTqcodcRH21mgyJkLApihekgf+3WZkfDiTOGYkKY0WOSOuNNhFEKv93/99D9708kjJ kXc0iI10apuksmKpCPCPcQFAD/FfRzLtxer2yBk6pzSPHai2xhGKp1UPvRhfhVqQCCyA QLmb/RUr3WlA0YEwscjBhxixfFYj6NlXj3l3fKQEMIgHt5mQrZ7iYh2dNRh9LkNZtbyH wxLxhnkTK0j+doc3I4nEu40GDA41YtcsTg9BzTZG8XHdBQxCrTnsD5bz1QR6oaBL1yKY pc9wgk3f8a3o/tUsOVWUVUbI4LLFqwMCyVEFm2mWnl0IjNoLleNb1Vv009INVPmSuxpV MXzg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y11-v6si4247602pgp.234.2018.06.21.10.18.51; Thu, 21 Jun 2018 10:19:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932902AbeFURRw (ORCPT + 99 others); Thu, 21 Jun 2018 13:17:52 -0400 Received: from mga18.intel.com ([134.134.136.126]:30223 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932800AbeFURRv (ORCPT ); Thu, 21 Jun 2018 13:17:51 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Jun 2018 10:17:50 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,252,1526367600"; d="scan'208";a="51190584" Received: from lmrad-mobl1.ger.corp.intel.com (HELO localhost) ([10.249.254.46]) by orsmga008.jf.intel.com with ESMTP; 21 Jun 2018 10:17:46 -0700 Date: Thu, 21 Jun 2018 20:17:46 +0300 From: Jarkko Sakkinen To: Tadeusz Struk 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" Subject: Re: [PATCH v3 0/2] tpm: add support for nonblocking operation Message-ID: <20180621171746.GJ11859@linux.intel.com> References: <152882630662.30206.8805136953394285180.stgit@tstruk-mobl1.jf.intel.com> <20180619131046.GC5609@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. /Jarkko