From: "Yang, Ziye" <ziye.yang@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] rte, eal: Rename pci_update_device and make it public
Date: Thu, 9 Mar 2017 23:04:17 +0000 [thread overview]
Message-ID: <FA6C2217B01E9D48A581BB48660210143988F463@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <3302470.dIBVR2JIfX@xps13>
Hi Thomas,
That's OK. Hope that the need of usage can be considered in the new framework.
-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
Sent: Friday, March 10, 2017 1:58 AM
To: Yang, Ziye <ziye.yang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] rte, eal: Rename pci_update_device and make it public
2017-02-13 10:53, Ziye Yang:
> The reaon is that sometimes we only like to rebound the kernel driver
> or VFIO or UIO or other drivers for this device after rte_eal_detach
> function. Function rte_eal_pci_probe_one not only updates the device
> but also probes the rte_eal_driver for this device, it is not
> flexible.
>
> Signed-off-by: Ziye Yang <ziye.yang@intel.com>
> ---
> lib/librte_eal/bsdapp/eal/eal_pci.c | 2 +-
> lib/librte_eal/common/eal_common_pci.c | 2 +-
> lib/librte_eal/common/eal_private.h | 13 -------------
> lib/librte_eal/common/include/rte_pci.h | 14 ++++++++++++++
> lib/librte_eal/linuxapp/eal/eal_pci.c | 2 +-
> 5 files changed, 17 insertions(+), 16 deletions(-)
The PCI bus management is going to change with the new bus framework.
Please check pending developments or future version for your needs.
This patch will be marked as rejected because of the conflicting work in progress.
prev parent reply other threads:[~2017-03-09 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 2:53 Ziye Yang
2017-03-09 17:58 ` Thomas Monjalon
2017-03-09 23:04 ` Yang, Ziye [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=FA6C2217B01E9D48A581BB48660210143988F463@shsmsx102.ccr.corp.intel.com \
--to=ziye.yang@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).