From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Roberto Sassu" <roberto.sassu@huaweicloud.com>,
"James Bottomley" <James.Bottomley@HansenPartnership.com>
Cc: <linux-integrity@vger.kernel.org>, "Mimi Zohar" <zohar@linux.ibm.com>
Subject: Re: TPM HMAC (really) bad performance
Date: Fri, 06 Sep 2024 17:40:40 +0300 [thread overview]
Message-ID: <D3ZA2MOLUMUR.3NEU8TFVD30SP@kernel.org> (raw)
In-Reply-To: <b8a7b3566e6014ba102ab98e10ede0d574d8930e.camel@huaweicloud.com>
On Fri Sep 6, 2024 at 3:32 PM EEST, Roberto Sassu wrote:
> Hi all
>
> when running the benchmark on my new component, the Integrity Digest
> Cache, I ran into a serious performance issue.
>
> The benchmark is extending a TPM PCR with 12313 entries of the IMA
> measurement list, and calculating the time elapsed for the operation.
>
> Without TPM HMAC: 102.8 seconds
>
> With TPM HMAC: 1941.71 seconds
>
>
> Do you have already an idea on how to improve the situation?
Some missing details: CPU architecture and TPM chip type.
Would be possible to generate off-CPU flame graph?
For decent instructions:
https://www.singlestore.com/blog/linux-off-cpu-investigation/
You can do post-processing steps "offline" only capture step would
need to be done in-target.
>
> Thanks
>
> Roberto
BR, Jarkko
next prev parent reply other threads:[~2024-09-06 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 12:32 TPM HMAC (really) bad performance Roberto Sassu
2024-09-06 14:31 ` James Bottomley
2024-09-06 14:40 ` Jarkko Sakkinen [this message]
2024-09-27 13:53 ` Roberto Sassu
2024-09-27 14:15 ` James Bottomley
2024-09-30 14:09 ` Mimi Zohar
2024-09-30 18:52 ` Mimi Zohar
2024-10-01 0:16 ` James Bottomley
2024-10-01 3:13 ` Mimi Zohar
2024-10-01 13:10 ` Mimi Zohar
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=D3ZA2MOLUMUR.3NEU8TFVD30SP@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-integrity@vger.kernel.org \
--cc=roberto.sassu@huaweicloud.com \
--cc=zohar@linux.ibm.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.