DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: "Gaëtan Rivet" <gaetan.rivet@6wind.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com,
	harry.van.haaren@intel.com, hemant.agrawal@nxp.com,
	gage.eads@intel.com, nipun.gupta@nxp.com
Subject: Re: [dpdk-dev] [PATCH] eventdev: remove PCI dependency
Date: Tue, 6 Jun 2017 14:31:18 +0530	[thread overview]
Message-ID: <20170606090117.GA25773@jerin> (raw)
In-Reply-To: <20170606080921.GK18840@bidouze.vm.6wind.com>

-----Original Message-----
> Date: Tue, 6 Jun 2017 10:09:21 +0200
> From: Gaëtan Rivet <gaetan.rivet@6wind.com>
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Cc: dev@dpdk.org, bruce.richardson@intel.com, harry.van.haaren@intel.com,
>  hemant.agrawal@nxp.com, gage.eads@intel.com, nipun.gupta@nxp.com
> Subject: Re: [dpdk-dev] [PATCH] eventdev: remove PCI dependency
> User-Agent: Mutt/1.5.23 (2014-03-12)
> 
> On Tue, Jun 06, 2017 at 08:35:48AM +0530, Jerin Jacob wrote:
> > -----Original Message-----
> > > Date: Mon, 5 Jun 2017 14:55:55 +0200
> > > From: Gaëtan Rivet <gaetan.rivet@6wind.com>
> > > To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> > > Cc: dev@dpdk.org, bruce.richardson@intel.com, harry.van.haaren@intel.com,
> > >  hemant.agrawal@nxp.com, gage.eads@intel.com, nipun.gupta@nxp.com
> > > Subject: Re: [dpdk-dev] [PATCH] eventdev: remove PCI dependency
> > > User-Agent: Mutt/1.5.23 (2014-03-12)
> > > 
> > > Hi Jerin,
> > 
> > Hi Gaëtan,
> > 
> > > 
> > > On Thu, Jun 01, 2017 at 10:11:46PM +0530, Jerin Jacob wrote:
> > > > Remove the PCI dependency from generic data structures
> > > > and moved the PCI specific code to rte_event_pmd_pci*
> > > > 
> > > 
> > > Thanks for working on this.
> > > 
> > > Do you plan on removing rte_pci.h in rte_eventdev_pmd.h? Do you think it
> > > would be feasible?
> > 
> > That is for PCI PMD specific probe(rte_event_pmd_pci_probe() and rte_event_pmd_pci_remove()),
> > More like, lib/librte_ether/rte_ethdev_pci.h functions in ethdev.
> > So, I think, It is OK to keep rte_pci.h for PMD specific functions.
> > 
> > 
> 
> Ok, sure. However rte_eventdev.c includes both rte_pci.h and
> rte_eventdev_pmd.h. Can it be made independent from the PMD specific
> include?

Sure. I will remove rte_pci.h from rte_eventdev.c and send the v2.

  reply	other threads:[~2017-06-06  9:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01 16:41 Jerin Jacob
2017-06-05 12:55 ` Gaëtan Rivet
2017-06-06  3:05   ` Jerin Jacob
2017-06-06  8:09     ` Gaëtan Rivet
2017-06-06  9:01       ` Jerin Jacob [this message]
2017-06-06 14:10 ` [dpdk-dev] [PATCH v2] " Jerin Jacob
2017-06-06 14:51   ` Gaëtan Rivet
2017-06-07  8:43   ` [dpdk-dev] [PATCH v2 0/4] Remove PCI and VDEV dependency from eventdev library Jerin Jacob
2017-06-07  8:43     ` [dpdk-dev] [PATCH v2 1/4] eventdev: remove PCI dependency from generic data structures Jerin Jacob
2017-06-09  8:37       ` [dpdk-dev] [PATCH v4 0/4] Remove PCI and VDEV dependency from eventdev library Jerin Jacob
2017-06-09  8:37         ` [dpdk-dev] [PATCH v4 1/4] eventdev: remove PCI dependency from generic data structures Jerin Jacob
2017-06-09  8:37         ` [dpdk-dev] [PATCH v4 2/4] eventdev: restructure event PMD release function Jerin Jacob
2017-06-09  8:37         ` [dpdk-dev] [PATCH v4 3/4] eventdev: make PCI probe and remove functions optional Jerin Jacob
2017-06-09  8:37         ` [dpdk-dev] [PATCH v4 4/4] eventdev: make vdev init and uninit " Jerin Jacob
2017-06-20 14:14         ` [dpdk-dev] [PATCH v4 0/4] Remove PCI and VDEV dependency from eventdev library Jerin Jacob
2017-06-07  8:43     ` [dpdk-dev] [PATCH v2 2/4] eventdev: restructure event PMD release function Jerin Jacob
2017-06-07  8:43     ` [dpdk-dev] [PATCH v2 3/4] eventdev: make PCI probe and remove functions optional Jerin Jacob
2017-06-07  8:43     ` [dpdk-dev] [PATCH v2 4/4] eventdev: make vdev init and uninit " Jerin Jacob
2017-06-07  9:27     ` [dpdk-dev] [PATCH v2 0/4] Remove PCI and VDEV dependency from eventdev library Gaëtan Rivet
2017-06-08 17:05       ` Jerin Jacob

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=20170606090117.GA25773@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=gaetan.rivet@6wind.com \
    --cc=gage.eads@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=nipun.gupta@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).