From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>, dev@dpdk.org
Cc: thomas.monjalon@6wind.com, bruce.richardson@intel.com,
shreyansh.jain@nxp.com, john.mcnamara@intel.com,
jerin.jacob@caviumnetworks.com
Subject: Re: [dpdk-dev] [PATCH v4 00/21] NXP DPAA2 FSLMC Bus driver
Date: Wed, 12 Apr 2017 14:49:44 +0100 [thread overview]
Message-ID: <15d51bdd-3b4b-5d00-3c06-965e990a9b30@intel.com> (raw)
In-Reply-To: <1491917847-3935-1-git-send-email-hemant.agrawal@nxp.com>
On 4/11/2017 2:37 PM, Hemant Agrawal wrote:
> (This patches has been split from DPAA2 PMD v8 series [1] as per
> comments received on ML [2].)
>
> For V3 - please check at [3].
>
> The patchset introduces NXP’s QorIQ-Layerscape DPAA2 Architecture based
> fsl-mc bus driver. This version of the driver supports NXP LS208xA,
> LS204xA and LS108x family of Network SoCs.
>
> This driver is base for DPAA2 based PMD to be introduced in later patches.
> It will be used by dpaa2 net, crypto, event & other devices.
> The details description of this bus along with PMD is part of later patch
> sets for introducing the NXP DPAA2 PMD.
>
> There are 3 main components of the FSLMC bus which enable the access to
> DPAA2 devices from userspace:
> 1) QBMAN hardware: Which enables application lock-less access to hardware
> queues and buffers.
> 2) MC or Management Complex: Layer between Userspace and elements on the
> FSLMC bus. This layer exposes underlying hardware as 'objects' and
> allows for their configuration. Some of the key objects exposed are:
> - DPNI, which refers to the network interface object.
> - DPBP, which refers to HW based memory pool object
> - DPIO, refers to processing context for accessing QBMAN
> 3) Portal: For accessing the hardware objects exposed by MC, a continuous
> mapped area is available in form of objects.
>
> This patchset introduces the above components.
>
> Future Changes/Caveats:
>
> 1) VFIO code for fsl-mc bus is different than eal-vfio code for pci bus.
> This need to be re-worked to make possible re-use of the existing code.
>
>
> References:
> [1] http://dpdk.org/ml/archives/dev/2017-March/059000.html
> [2] http://dpdk.org/ml/archives/dev/2017-March/059789.html
> [3] http://dpdk.org/ml/archives/dev/2017-April/063480.html
> ---
> v4:
> * rebased on net-next (135b3f60b)
> * removing config dependency in make file
> * minor error handling cases
>
> v3:
> * rebased on master (17.05-rc1)
> * error handling in scan & probe
>
> v2:
> * rebased on next-net (b36be54c)
> * removing "-Wno-strict-alias" from makefile
>
> Hemant Agrawal (21):
> mk/dpaa2: add the crc support to the machine type
> bus/fslmc: introducing fsl-mc bus driver
> bus/fslmc: add QBMAN driver to bus
> bus/fslmc: introduce MC object functions
> bus/fslmc: add mc dpio object support
> bus/fslmc: add mc dpbp object support
> eal/vfio: adding vfio utility functions in map file
> bus/fslmc: add vfio support
> bus/fslmc: scan for net and sec device
> bus/fslmc: add debug log support
> bus/fslmc: dpio portal driver
> bus/fslmc: introduce support for hardware mempool object
> bus/fslmc: affine dpio to crypto threads
> bus/fslmc: define queues for DPAA2 devices
> bus/fslmc: define hardware annotation area size
> bus/fslmc: introduce true and false macros
> bus/fslmc: define VLAN header length
> bus/fslmc: add packet FLE definitions
> bus/fslmc: add physical-virtual address translation helpers
> bus/fslmc: add support for DMA mapping for ARM SMMU
> bus/fslmc: frame queue based dq storage alloc
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-04-12 13:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 13:37 Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 01/21] mk/dpaa2: add the crc support to the machine type Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 02/21] bus/fslmc: introducing fsl-mc bus driver Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 03/21] bus/fslmc: add QBMAN driver to bus Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 04/21] bus/fslmc: introduce MC object functions Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 05/21] bus/fslmc: add mc dpio object support Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 06/21] bus/fslmc: add mc dpbp " Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 07/21] eal/vfio: adding vfio utility functions in map file Hemant Agrawal
2017-04-12 13:49 ` Ferruh Yigit
2017-04-13 6:47 ` Shreyansh Jain
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 08/21] bus/fslmc: add vfio support Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 09/21] bus/fslmc: scan for net and sec device Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 10/21] bus/fslmc: add debug log support Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 11/21] bus/fslmc: dpio portal driver Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 12/21] bus/fslmc: introduce support for hardware mempool object Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 13/21] bus/fslmc: affine dpio to crypto threads Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 14/21] bus/fslmc: define queues for DPAA2 devices Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 15/21] bus/fslmc: define hardware annotation area size Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 16/21] bus/fslmc: introduce true and false macros Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 17/21] bus/fslmc: define VLAN header length Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 18/21] bus/fslmc: add packet FLE definitions Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 19/21] bus/fslmc: add physical-virtual address translation helpers Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 20/21] bus/fslmc: add support for DMA mapping for ARM SMMU Hemant Agrawal
2017-04-11 13:37 ` [dpdk-dev] [PATCH v4 21/21] bus/fslmc: frame queue based dq storage alloc Hemant Agrawal
2017-04-12 13:49 ` Ferruh Yigit [this message]
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=15d51bdd-3b4b-5d00-3c06-965e990a9b30@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=john.mcnamara@intel.com \
--cc=shreyansh.jain@nxp.com \
--cc=thomas.monjalon@6wind.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).