From: Ziye Yang <ziye.yang@intel.com>
To: dev@dpdk.org
Cc: Ziye <ziye.yang@intel.com>
Subject: [dpdk-dev] [PATCH] PCI: ABI change request for adding new field in rte_pci_id structure
Date: Mon, 25 Jan 2016 10:36:59 +0800 [thread overview]
Message-ID: <1453689419-237252-1-git-send-email-ziye.yang@intel.com> (raw)
From: Ziye <ziye.yang@intel.com>
The purpose of this patch is used to add a new field
"class" in rte_pci_id structure. The new class field includes
class_id, subcalss_id, programming interface of a pci device.
With this field, we can identify pci device by its class info,
which can be more flexible instead of probing the device by
vendor_id OR device_id OR subvendor_id OR subdevice_id.
For example, we can probe all nvme devices by class field, which
can be quite convenient.
Signed-off-by: Ziye Yang <ziye.yang@intel.com>
---
doc/guides/rel_notes/release_2_3.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/rel_notes/release_2_3.rst b/doc/guides/rel_notes/release_2_3.rst
index 99de186..8fcb43f 100644
--- a/doc/guides/rel_notes/release_2_3.rst
+++ b/doc/guides/rel_notes/release_2_3.rst
@@ -39,6 +39,10 @@ API Changes
ABI Changes
-----------
+* New field ``class`` is added into ``rte_pci_id`` structure. This new
+ added ``class`` field can be used to probe pci devices by class related
+ info. With this new field, the size of structure ``rte_pci_device`` will
+ be increased.
Shared Library Versions
-----------------------
--
1.9.3
next reply other threads:[~2016-01-25 2:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 2:36 Ziye Yang [this message]
2016-02-16 4:15 ` [dpdk-dev] [PATCH v2] " Ziye Yang
2016-02-16 10:11 ` Bruce Richardson
2016-02-16 10:34 ` Thomas Monjalon
2016-02-17 1:54 ` [dpdk-dev] [PATCH v3] " Ziye Yang
2016-02-17 10:14 ` Bruce Richardson
2016-04-05 15:31 ` Thomas Monjalon
2016-02-18 1:57 ` Zhang, Helin
2016-02-18 2:46 ` Liang, Cunming
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=1453689419-237252-1-git-send-email-ziye.yang@intel.com \
--to=ziye.yang@intel.com \
--cc=dev@dpdk.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).