From: "Wiles, Keith" <keith.wiles@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Chen, Jing D" <jing.d.chen@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Rogers, Gerald" <gerald.rogers@intel.com>
Subject: Re: [dpdk-dev] [RFC 2/2] prgdev: introduce generic prgdev API
Date: Wed, 8 Feb 2017 23:06:51 +0000 [thread overview]
Message-ID: <EABD0B8C-FECB-4E7D-99D8-6268A1324C9C@intel.com> (raw)
In-Reply-To: <20170208144945.0ce116ee@xeon-e3>
> On Feb 8, 2017, at 4:49 PM, Stephen Hemminger <stephen@networkplumber.org> wrote:
>
> On Fri, 20 Jan 2017 11:21:38 +0800
> "Chen Jing D(Mark)" <jing.d.chen@intel.com> wrote:
>
>> +struct rte_prg_dev_info {
>> + struct rte_pci_device *pci_dev; /**< Device PCI information. */
>
> NAK
>
> No new API should refer to PCI devices. We are trying to make all references
> to devices generic. Crypto suceeded, ether is in process, but no new ones please.
The design is not PCI centric and should not be PCI centric, it is just what they started with months ago. So please look past the PCI bits as they have not integrated into the latest code base yet.
Regards,
Keith
next prev parent reply other threads:[~2017-02-08 23:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 3:21 [dpdk-dev] [RFC 0/2] Prgdev API Chen Jing D(Mark)
2017-01-20 3:21 ` [dpdk-dev] [RFC 1/2] doc: introduction to prgdev Chen Jing D(Mark)
2017-02-01 11:41 ` Jan Blunck
2017-02-03 9:21 ` Liang, Cunming
2017-02-06 9:16 ` Chen, Jing D
2017-02-08 3:30 ` Liang, Cunming
2017-01-20 3:21 ` [dpdk-dev] [RFC 2/2] prgdev: introduce generic prgdev API Chen Jing D(Mark)
2017-02-08 22:49 ` Stephen Hemminger
2017-02-08 23:06 ` Wiles, Keith [this message]
2017-02-09 2:23 ` Chen, Jing D
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=EABD0B8C-FECB-4E7D-99D8-6268A1324C9C@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=gerald.rogers@intel.com \
--cc=jing.d.chen@intel.com \
--cc=stephen@networkplumber.org \
/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).