<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I’ve gone down the path of exploring parallelization of crypto in Strongswan from [1].<div class=""><br class=""></div><div class="">It seems to be working as a) the expected output shows up in ‘cat /proc/crypto’ and b) under load in htop, it’s now showing kernel activity on all cores vs. a single core before (not sophisticated, but it definitely changed after the modprobe).</div><div class=""><br class=""></div><div class="">My question to the group is, how does one make it stick across boots? I tried the trick of putting the modprobe in /etc/rc.local and That Was Bad (continuous reboot loop). Backed it out and we’re ok. Obviously there has to be a better way. Wondering what the proper way in Centos 7 is for this module.</div><div class=""><br class=""></div><div class="">The process in [2] doesn’t seem to work for installing them.</div><div class=""><br class=""></div><div class="">Thanks for sharing any experiences.</div><div class=""><br class=""></div><div class="">EKG</div><div class=""><br class=""></div><div class="">[1] <a href="https://wiki.strongswan.org/projects/strongswan/wiki/Pcrypt" class="">https://wiki.strongswan.org/projects/strongswan/wiki/Pcrypt</a></div><div class="">[2] <a href="https://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-kernel-modules-persistant.html" class="">https://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-kernel-modules-persistant.html</a></div></body></html>