DPDK usage discussions
 help / color / mirror / Atom feed
* [dpdk-users] Best Practices for key storage
@ 2019-11-15 17:46 Eric Kuha
  0 siblings, 0 replies; only message in thread
From: Eric Kuha @ 2019-11-15 17:46 UTC (permalink / raw)
  To: users


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,

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-11-15 17:46 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-15 17:46 [dpdk-users] Best Practices for key storage Eric Kuha

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git