DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jianfeng Tan <jianfeng.tan@intel.com>
To: dev@dpdk.org
Cc: john.mcnamara@intel.com, yuanhan.liu@linux.intel.com,
	stephen@networkplumber.org, Jianfeng Tan <jianfeng.tan@intel.com>
Subject: [dpdk-dev] [PATCH 3/3] doc: remove ABI changes in igb_uio
Date: Tue, 24 Jan 2017 07:34:08 +0000	[thread overview]
Message-ID: <1485243248-27082-4-git-send-email-jianfeng.tan@intel.com> (raw)
In-Reply-To: <1485243248-27082-1-git-send-email-jianfeng.tan@intel.com>

We announced ABI changes to remove iomem and ioport mapping in
igb_uio. But it has potential backward compatibility issue: cannot
run old version DPDK on modified igb_uio.

The purpose of this changes was to fix a bug: when DPDK app crashes,
those devices by igb_uio are not stopped either DPDK PMD driver or
igb_uio driver. We need to figure out new way to fix this bug.

Fixes: 3bac1dbc1ed ("doc: announce iomem and ioport removal from igb_uio")

Suggested-by: Stephen Hemminger <stephen@networkplumber.org>
Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
---
 doc/guides/rel_notes/deprecation.rst | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 755dc65..0f039dd 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -8,11 +8,6 @@ API and ABI deprecation notices are to be posted here.
 Deprecation Notices
 -------------------
 
-* igb_uio: iomem mapping and sysfs files created for iomem and ioport in
-  igb_uio will be removed, because we are able to detect these from what Linux
-  has exposed, like the way we have done with uio-pci-generic. This change
-  targets release 17.02.
-
 * ABI/API changes are planned for 17.02: ``rte_device``, ``rte_driver`` will be
   impacted because of introduction of a new ``rte_bus`` hierarchy. This would
   also impact the way devices are identified by EAL. A bus-device-driver model
-- 
2.7.4

  parent reply	other threads:[~2017-01-24  7:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24  7:34 [dpdk-dev] [PATCH 0/3] doc upates Jianfeng Tan
2017-01-24  7:34 ` [dpdk-dev] [PATCH 1/3] doc: add guide to use virtio_user for container networking Jianfeng Tan
2017-01-24  7:34 ` [dpdk-dev] [PATCH 2/3] doc: add guide to use virtio_user as exceptional path Jianfeng Tan
2017-01-24  7:34 ` Jianfeng Tan [this message]
2017-01-24 13:35   ` [dpdk-dev] [PATCH 3/3] doc: remove ABI changes in igb_uio Ferruh Yigit
2017-01-30 17:52     ` Thomas Monjalon
2017-02-01  7:24       ` Tan, Jianfeng
2017-02-09 14:45 ` [dpdk-dev] [PATCH 0/3] doc upates Thomas Monjalon
2017-02-09 16:06 ` [dpdk-dev] [PATCH v2 " Jianfeng Tan
2017-02-09 16:06   ` [dpdk-dev] [PATCH v2 1/3] doc: add guide to use virtio_user for container networking Jianfeng Tan
2017-02-09 16:06   ` [dpdk-dev] [PATCH v2 2/3] doc: add guide to use virtio_user as exceptional path Jianfeng Tan
2017-02-09 16:06   ` [dpdk-dev] [PATCH v2 3/3] doc: postpone ABI changes in igb_uio Jianfeng Tan
2017-02-09 17:40     ` Ferruh Yigit
2017-02-10 10:44       ` Thomas Monjalon
2017-02-10 11:20         ` Tan, Jianfeng

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=1485243248-27082-4-git-send-email-jianfeng.tan@intel.com \
    --to=jianfeng.tan@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=yuanhan.liu@linux.intel.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).