[dpdk-dev] [PATCH 1/2] cryptodev: change queue pair configure structure

[Zhang, Roy Fan]

Hi Konstantin,

Ah, sorry they are added by mistake. Will not happen in V2.

Regards,
fan

> -----Original Message-----
> From: Ananyev, Konstantin
> Sent: Friday, November 16, 2018 12:06 PM
> To: Zhang, Roy Fan <roy.fan.zhang at intel.com>; dev at dpdk.org
> Cc: akhil.goyal at nxp.com
> Subject: RE: [dpdk-dev] [PATCH 1/2] cryptodev: change queue pair configure
> structure
> 
> Hi Fan,
> 
> > --- a/config/common_base
> > +++ b/config/common_base
> > @@ -446,7 +446,7 @@ CONFIG_RTE_LIBRTE_VDEV_NETVSC_PMD=n
> >  #
> >  # Compile null PMD
> >  #
> > -CONFIG_RTE_LIBRTE_PMD_NULL=y
> > +CONFIG_RTE_LIBRTE_PMD_NULL=n
> >
> >  #
> >  # Compile software PMD backed by PCAP files @@ -525,13 +525,13 @@
> > CONFIG_RTE_LIBRTE_DPAA_MAX_CRYPTODEV=4
> >  #
> >  # Compile PMD for Cavium OCTEON TX crypto device  #
> > -CONFIG_RTE_LIBRTE_PMD_OCTEONTX_CRYPTO=y
> > +CONFIG_RTE_LIBRTE_PMD_OCTEONTX_CRYPTO=n
> >
> >  #
> >  # Compile PMD for QuickAssist based devices - see docs for details  #
> > CONFIG_RTE_LIBRTE_PMD_QAT=y -
> CONFIG_RTE_LIBRTE_PMD_QAT_SYM=n
> > +CONFIG_RTE_LIBRTE_PMD_QAT_SYM=y
> >  #
> >  # Max. number of QuickAssist devices, which can be detected and
> > attached  # @@ -551,33 +551,33 @@
> CONFIG_RTE_MAX_VIRTIO_CRYPTO=32  #
> > # Compile PMD for AESNI backed device  #
> > -CONFIG_RTE_LIBRTE_PMD_AESNI_MB=n
> > +CONFIG_RTE_LIBRTE_PMD_AESNI_MB=y
> >
> >  #
> >  # Compile PMD for Software backed device
> >  #
> > -CONFIG_RTE_LIBRTE_PMD_OPENSSL=n
> > +CONFIG_RTE_LIBRTE_PMD_OPENSSL=y
> >
> >  #
> >  # Compile PMD for AESNI GCM device
> >  #
> > -CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=n
> > +CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y
> >
> >  #
> >  # Compile PMD for SNOW 3G device
> >  #
> > -CONFIG_RTE_LIBRTE_PMD_SNOW3G=n
> > +CONFIG_RTE_LIBRTE_PMD_SNOW3G=y
> >  CONFIG_RTE_LIBRTE_PMD_SNOW3G_DEBUG=n
> >
> >  #
> >  # Compile PMD for KASUMI device
> >  #
> > -CONFIG_RTE_LIBRTE_PMD_KASUMI=n
> > +CONFIG_RTE_LIBRTE_PMD_KASUMI=y
> >
> >  #
> >  # Compile PMD for ZUC device
> >  #
> > -CONFIG_RTE_LIBRTE_PMD_ZUC=n
> > +CONFIG_RTE_LIBRTE_PMD_ZUC=y
> >
> >  # Compile PMD for Crypto Scheduler device
> >  #
> > @@ -601,7 +601,7 @@ CONFIG_RTE_LIBRTE_PMD_MVSAM_CRYPTO=n
> >  #
> >  # Compile generic security library
> >  #
> > -CONFIG_RTE_LIBRTE_SECURITY=y
> > +CONFIG_RTE_LIBRTE_SECURITY=n
> >
> >  #
> >  # Compile generic compression device library
> > @@ -842,7 +842,7 @@ CONFIG_RTE_LIBRTE_METER=y
> >  #
> >  # Compile librte_classify
> >  #
> > -CONFIG_RTE_LIBRTE_FLOW_CLASSIFY=y
> > +CONFIG_RTE_LIBRTE_FLOW_CLASSIFY=n
> >
> >  #
> >  # Compile librte_sched
> > @@ -939,7 +939,7 @@ CONFIG_RTE_PROC_INFO=n
> >  #
> >  # Compile the PMD test application
> >  #
> > -CONFIG_RTE_TEST_PMD=y
> > +CONFIG_RTE_TEST_PMD=n
> >  CONFIG_RTE_TEST_PMD_RECORD_CORE_CYCLES=n
> >  CONFIG_RTE_TEST_PMD_RECORD_BURST_STATS=n
> >
> 
> Not sure why config changes are needed.
> Guess just by mistake?
> Konstantin