>
> > >
> > > This multi process app is only taking care of crypto queues while others
> > > are
> > > for NICs.
> > > Is it not worth to have crypto+NIC multi process app instead of this app?
> > [Arek] - initially main purpose was to check PMD behavior when:
> > 1) configure cryptodev, sessions, queues and do enqueue/dequeue from
> another different processes
> > 2) run enqueue/dequeue from different processes on the same queue pair.
> > If it can be done with one app I think it is ok.
> > > I believe most common usecases of crypto are with network traffic.
> > > Can we modify l2fwd-crypto for multi process?
> [Fiona] Yes, it would be a good idea to do that sample app too.
> However this app allows standalone validation of cryptodev lib and PMDs,
> running in multiple processes, without introducing dependencies on
> ethdev APIs, traffic generator, NIC, etc. I think this is useful as is.
> One consideration is whether it would be better to treat this as a test tool
> and move to the test directory - as you're right, it's not showing
> a typical complete application, just allowing to play around with the crypto
> part.
> My preference is to move to under the examples/multi-process, but up to you.
>
Example applications are also not close to real work application. But they
should
Have end to end functionality available with some missing processing in between.
I would say:
- modifying l2fwd-crypto can be preference 1
- moving multiprocess crypto to test app can be preference 2 as it is just a
unit test application for multi process.
- moving to examples/multi-process will be preference 3.
