From: Thomas Monjalon <thomas@monjalon.net>
To: Shreyansh Jain <shreyansh.jain@nxp.com>, hemant.agrawal@nxp.com
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/6] NXP DPAA2: Refactor bus scan/probe code
Date: Fri, 06 Oct 2017 01:09:48 +0200 [thread overview]
Message-ID: <8620733.AHIAvCD8Yy@xps> (raw)
In-Reply-To: <cac5f970-0a4e-14ca-9866-885e9e4c4a73@intel.com>
11/09/2017 16:06, Ferruh Yigit:
> On 8/25/2017 11:19 AM, Shreyansh Jain wrote:
> > Change Log:
> > ~~~~~~~~~~~
> > v2:
> > - Minor updates for logging (removed some logs and changed others
> > to make it cleaner when application starts)
> >
> > Brief:
> > ~~~~~~
> >
> > -- v1 is at [3] --
> >
> > In [1], during the IOVA Mapping patch set [2] discussion, it was
> > observed that DPAA2 scan was actually doing work meant for probing.
> >
> > This patchset demarcates the roles of FSLMC bus scan and probe
> > functions much more clearly than before:
> >
> > 1. scan now only add devices into a list
> > unlike previously, scan doesn't initialize the devices using the VFIO
> > operations. Now, scan would only add the devices onto a local device
> > list after marking their type and filling in device name.
> >
> > 2. probe would now perform VFIO operations
> > in dpaa2, for the device added in list, an initialization needs
> > to be done so as to enable the devices - before actually API calls
> > can be served. Probe function now initializes the devices as well
> > as links then to the Eth/Crypto drivers.
> >
> > 3. Refactoring some VFIO code
> > This patch improves the overall code contained within DPAA2 bus
> > for DPAA2 VFIO layer.
> >
> > [1] http://dpdk.org/ml/archives/dev/2017-July/071270.html
> > [2] http://dpdk.org/ml/archives/dev/2017-July/070833.html
> > [3] http://dpdk.org/ml/archives/dev/2017-August/073011.html
> >
> > Shreyansh Jain (6):
> > bus/fslmc: support only single group and container
> > bus/fslmc: introduce new device type enumerator
> > crypto/dpaa2_sec: update driver type field
> > net/dpaa2: update driver type field
> > drivers: refactor DPAA2 object definition
> > bus/fslmc: refactor scan and probe functions
>
> Series Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> I guess this set needs to go in to the main tree, because of both
> - as far as I get IOVA patchset breaks dpaa2, so this should go in
> before that patchset
> - This patchset has both crypto and net patches, hard to get by sub-trees
Applied, thanks
prev parent reply other threads:[~2017-10-05 23:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 12:51 [dpdk-dev] [PATCH " Shreyansh Jain
2017-08-18 12:51 ` [dpdk-dev] [PATCH 1/6] bus/fslmc: support only single group and container Shreyansh Jain
2017-08-18 12:51 ` [dpdk-dev] [PATCH 2/6] bus/fslmc: introduce new device type enumerator Shreyansh Jain
2017-08-18 12:51 ` [dpdk-dev] [PATCH 3/6] net/dpaa2: update driver type field Shreyansh Jain
2017-08-18 12:51 ` [dpdk-dev] [PATCH 4/6] crypto/dpaa2_sec: " Shreyansh Jain
2017-08-18 12:51 ` [dpdk-dev] [PATCH 5/6] drivers: refactor DPAA2 object definition Shreyansh Jain
2017-08-18 12:51 ` [dpdk-dev] [PATCH 6/6] bus/fslmc: refactor scan and probe functions Shreyansh Jain
2017-08-25 10:19 ` [dpdk-dev] [PATCH v2 0/6] NXP DPAA2: Refactor bus scan/probe code Shreyansh Jain
2017-08-25 10:19 ` [dpdk-dev] [PATCH v2 1/6] bus/fslmc: support only single group and container Shreyansh Jain
2017-09-18 11:15 ` santosh
2017-08-25 10:19 ` [dpdk-dev] [PATCH v2 2/6] bus/fslmc: introduce new device type enumerator Shreyansh Jain
2017-08-25 10:19 ` [dpdk-dev] [PATCH v2 3/6] crypto/dpaa2_sec: update driver type field Shreyansh Jain
2017-08-25 10:19 ` [dpdk-dev] [PATCH v2 4/6] net/dpaa2: " Shreyansh Jain
2017-08-25 10:19 ` [dpdk-dev] [PATCH v2 5/6] drivers: refactor DPAA2 object definition Shreyansh Jain
2017-08-25 10:19 ` [dpdk-dev] [PATCH v2 6/6] bus/fslmc: refactor scan and probe functions Shreyansh Jain
2017-09-11 14:06 ` [dpdk-dev] [PATCH v2 0/6] NXP DPAA2: Refactor bus scan/probe code Ferruh Yigit
2017-09-11 14:25 ` Shreyansh Jain
2017-09-25 7:07 ` Hemant Agrawal
2017-09-18 14:36 ` santosh
2017-10-05 23:09 ` Thomas Monjalon [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=8620733.AHIAvCD8Yy@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=shreyansh.jain@nxp.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).