FYI for those not on IRC... just posted these comments. Feel free to reply here or there. FYI here's the latest patch that, for AESNI, is fully functional. https://review.gerrithub.io/#/c/403107/
peluse> jimharris, or anyone interested in the ongoing crypto work... have a few options to consider
<peluse> right now, the proposed RFC patch supports the virtual PMD that does AES-NI CBC and that's all it supports
<peluse> one path forward would be a different vbdev per PMD (different DPDK virtual PMD or HW like Intel QAT)
<peluse> however since DPDK has a unified API called crypto dev so we don't have to go that route
<peluse> we can have just one, slightly more complicated vbdev, where multiple PMDs virtual types as well as HW can be supported and chosen via config file
<peluse> The latter seems like the best option but before I embark on that design based on the current RFC patch wanted to get some feedback...
<peluse> (the former would have a few benefits though, mainly keeping a vbdev simple per PMD for those who aren't interested in multiple drivers and/or mixing HW and virtual PMDs)
I would like to use spdk for a product.
I have a user space application which should serve as the backstore.
How do I connect it to spdk?
I saw that if I want to use ready backstores like Malloc or Null I can simply specify them in a configuration file and spdk will create them for me.
How do I do that with my application?
Is there any example?