DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mokhtar, Amr" <amr.mokhtar@intel.com>
To: "Peng, Yuan" <yuan.peng@intel.com>,
	"Chalupnik, KamilX" <kamilx.chalupnik@intel.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Chalupnik, KamilX" <kamilx.chalupnik@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/testbbdev: fix inputs mbuf creation issue
Date: Fri, 17 Aug 2018 10:34:16 +0000	[thread overview]
Message-ID: <3D3765A8CDB52A4C8B410430AA19CB23708C95E8@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <67D543A150B29E4CAAE53918F64EDAEA375E4D28@SHSMSX103.ccr.corp.intel.com>


> -----Original Message-----
> From: Peng, Yuan
> Sent: Friday 17 August 2018 10:39
> To: Chalupnik, KamilX <kamilx.chalupnik@intel.com>; Mokhtar, Amr
> <amr.mokhtar@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org; Chalupnik, KamilX
> <kamilx.chalupnik@intel.com>; Peng, Yuan <yuan.peng@intel.com>
> Subject: RE: [dpdk-dev] [PATCH] app/testbbdev: fix inputs mbuf creation
> issue
> 
> Tested-by: Peng, Yuan <yuan.peng@intel.com>
> 
> > NIC Fortville 4*10G
> > ethtool -i ens785f1
> > driver: i40e
> > version: 2.4.10
> > firmware-version: 6.01 0x80003205 1.1691.0 DPDK version: 18.11-rc0
> > commit 76b9d9de5c7d747c381027156aac07735cb1bc0c
> > FlexRAN-1.6.0
> > Os: 4.4.0-62-generic
> > ICC:parallel_studio_xe_2018_update1_professional_edition_for_cpp
> > Set ``CONFIG_RTE_LIBRTE_PMD_BBDEV_TURBO_SW=y``
> > cat /proc/cmdline
> > BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=673a4478-
> afa5-
> > 463a-afa2-40681423994e ro hugepagesz=1G hugepages=16
> > default_hugepagesz=1G isolcpus=1-43 intel_iommu=on nohz_full=1-43
> > rcu_nocbs=1-43 iommu=pt
> >
> > ./usertools/dpdk-devbind.py -b vfio-pci 05:00.0 05:00.1
> > ./app/test-bbdev/test-bbdev.py -e="--
> > vdev=baseband_null,socket_id=0,max_nb_queues=8"
> >
> > the case can passed.
> >
> > Thanks.
> > Yuan.
> 
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kamil Chalupnik
> Sent: Friday, August 17, 2018 3:19 PM
> To: Mokhtar, Amr <amr.mokhtar@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org; Chalupnik, KamilX
> <kamilx.chalupnik@intel.com>
> Subject: [dpdk-dev] [PATCH] app/testbbdev: fix inputs mbuf creation issue
> 
> Omitting inputs and outputs mbuf creation for BaseBand Null Device as
> inputs and outputs data do not exist for Null Device
> 
> Fixes: b2a4654f082b ("mempool: check for zero size creation")
> Cc: pablo.de.lara.guarch@intel.com
> 
> Signed-off-by: Kamil Chalupnik <kamilx.chalupnik@intel.com>

Acked-by: Amr Mokhtar <amr.mokhtar@intel.com>

  reply	other threads:[~2018-08-17 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17  7:19 Kamil Chalupnik
2018-08-17  9:39 ` Peng, Yuan
2018-08-17 10:34   ` Mokhtar, Amr [this message]
2018-08-23 13:54 ` Akhil Goyal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D3765A8CDB52A4C8B410430AA19CB23708C95E8@IRSMSX104.ger.corp.intel.com \
    --to=amr.mokhtar@intel.com \
    --cc=dev@dpdk.org \
    --cc=kamilx.chalupnik@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=stable@dpdk.org \
    --cc=yuan.peng@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).