public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	peterhuewe@gmx.de, gregkh@linuxfoundation.org,
	"open list:KEYS-TRUSTED" <keyrings@vger.kernel.org>,
	"open list:KEYS-TRUSTED" <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] Basic trusted keys support for TPM 2.0
Date: Tue, 13 Oct 2015 11:41:20 -0600	[thread overview]
Message-ID: <20151013174120.GC22160@obsidianresearch.com> (raw)
In-Reply-To: <1444723889-11650-1-git-send-email-jarkko.sakkinen@linux.intel.com>

On Tue, Oct 13, 2015 at 11:11:21AM +0300, Jarkko Sakkinen wrote:

> * I updated tpm_buf to a be heap based structure. Now there's one full
>   page of memory for variable sized messages. Also the stack is greatly
>   reduced.

You may as well just use a skb then.

Jason

  parent reply	other threads:[~2015-10-13 17:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13  8:11 [PATCH v2 0/4] Basic trusted keys support for TPM 2.0 Jarkko Sakkinen
2015-10-13  8:11 ` [PATCH v2 1/4] tpm: introduce tpm_buf Jarkko Sakkinen
2015-10-13  8:11 ` [PATCH v2 2/4] keys, trusted: move struct trusted_key_options to trusted-type.h Jarkko Sakkinen
2015-10-13  8:11 ` [PATCH v2 3/4] tpm: seal/unseal for TPM 2.0 Jarkko Sakkinen
2015-10-13  8:11 ` [PATCH v2 4/4] keys, trusted: seal/unseal with TPM 2.0 chips Jarkko Sakkinen
2015-10-13  8:53 ` [PATCH v2 0/4] Basic trusted keys support for TPM 2.0 Jarkko Sakkinen
2015-10-13 17:41 ` Jason Gunthorpe [this message]
2015-10-13 19:25   ` Jarkko Sakkinen
2015-10-16 16:21 ` David Howells
2015-10-16 18:30   ` Jarkko Sakkinen

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=20151013174120.GC22160@obsidianresearch.com \
    --to=jgunthorpe@obsidianresearch.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=tpmdd-devel@lists.sourceforge.net \
    /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