Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

Need more investigation on stack optimization when creating Aes256GcmKeyBuffer inside test_idekm_tdisp #192

Open
longlongyang opened this issue Dec 29, 2023 · 0 comments

Comments

@longlongyang
Copy link
Contributor

longlongyang commented Dec 29, 2023

REF: #186 , #191

Currently, when creating Aes256GcmKeyBuffer inside function test_idekm_tdisp, using below command to run requester will result in a big stack consumption.

cargo run --release -p spdm-requester-emu --no-default-features --features=spdm-ring,hashed-transcript-data,test_stack_size,test_heap_size,is_sync

While as PR #191 does, moving the Aes256GcmKeyBuffer creation out of function test_idekm_tdisp, the stack consumption of function test_idekm_tdisp can be optimized a lot. Need to root cause this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant