From: Eric Kuha <kuhax005@umn.edu>
To: users@dpdk.org
Subject: [dpdk-users] Best Practices for key storage
Date: Fri, 15 Nov 2019 11:46:10 -0600 [thread overview]
Message-ID: <CAG1M=GAo4n2b=RYf3KkqVP8YtMACTP9M3tu-pKCH2_NMjpxxhA@mail.gmail.com> (raw)
Hello,
Using openssl encryption to generate long-term and ephemeral keys for
asymmetric crypto sessions. What are the best practices for storing the
keys that have not yet expired? Clearly, storing them via rte_zmalloc() is
not desirable since it requires a lot of overhead, but I don't necessarily
want them sitting around in my op pool (or do I?).
When they are generated they are allocated in the crypto op pool. Should I
just not free the op struct and leave it in the pool for future operations?
Or should I copy the data to some other location for more semi-permanent
use and free the op struct?
Should they be allocated in a special key mempool? Or is there some other
best practice that is advised by the community/devs?
Many thanks,
Eric
reply other threads:[~2019-11-15 17:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAG1M=GAo4n2b=RYf3KkqVP8YtMACTP9M3tu-pKCH2_NMjpxxhA@mail.gmail.com' \
--to=kuhax005@umn.edu \
--cc=users@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).