[dpdk-dev] [PATCH] app/bbdev: update test vectors

Mokhtar, Amr amr.mokhtar at intel.com
Tue Apr 24 17:41:02 CEST 2018



> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Tuesday 24 April 2018 15:57
> To: Chalupnik, KamilX <kamilx.chalupnik at intel.com>; dev at dpdk.org
> Cc: Mokhtar, Amr <amr.mokhtar at intel.com>; Chalupnik, KamilX
> <kamilx.chalupnik at intel.com>
> Subject: RE: [dpdk-dev] [PATCH] app/bbdev: update test vectors
> 
> 
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of KamilX Chalupnik
> > Sent: Wednesday, April 4, 2018 3:06 PM
> > To: dev at dpdk.org
> > Cc: Mokhtar, Amr <amr.mokhtar at intel.com>; Chalupnik, KamilX
> > <kamilx.chalupnik at intel.com>
> > Subject: [dpdk-dev] [PATCH] app/bbdev: update test vectors
> >
> > From: "Chalupnik, KamilX" <kamilx.chalupnik at intel.com>
> >
> > Update test vectors directory for Wireless Baseband Device:
> > - creation of new vectors to test and validate BBDevice capabilities
> > - python script used for tests execution updated
> >
> > Update the test app documentation:
> > - vector test names updated
> > - description of tests added
> > - usage of test app updated
> >
> > Signed-off-by: KamilX Chalupnik <kamilx.chalupnik at intel.com>
> 

<...> 

>
> >
> >    ./test-bbdev.py -p ../../x86_64-native-linuxapp-icc/app/testbbdev
> > -  -v ./test_vectors/bbdev_vector_td_default.data
> > +  -v turbo_dec_default.data
> 
> Shouldn't this be still under test_vectors?

This is only a soft link to the test vector (that is located inside ./test_vectors)
that will be used as a default one. This is for the user's convenience to keep
running the test using one command.
This approach also prevents replicating the test vector or changing the TV filename.
The filename by its own should be quite descriptive of all various parameters used in
the test like C, K, E, ...



More information about the dev mailing list