On 4/10/2018 2:19 PM, Burakov, Anatoly wrote:
> On 10-Apr-18 11:55 AM, Tosatti, Giovanni wrote:
>> This patch adds a " --restore" option that will unbind all devices currently
>> bound to DPDK PMDs back to the kernel driver.
>>
>> ---
>> /opt/Perforce/gtosatti_centos/E-XMS/CSA-Mainline/Third-Part
On 10-Apr-18 11:55 AM, Tosatti, Giovanni wrote:
This patch adds a " --restore" option that will unbind all devices currently
bound to DPDK PMDs back to the kernel driver.
---
/opt/Perforce/gtosatti_centos/E-XMS/CSA-Mainline/Third-Party/dpdk/dpdk-16.07.orig/tools/dpdk-devbind.py
+++
/opt/Perfo
On 10-Apr-18 11:55 AM, Tosatti, Giovanni wrote:
This patch adds a " --restore" option that will unbind all devices currently
bound to DPDK PMDs back to the kernel driver.
Hi Giovanni,
Nitpicking the commit message, but I believe "unbind" here is a bit of a
misnomer - one does not "unbind to
---
/opt/Perforce/gtosatti_centos/E-XMS/CSA-Mainline/Third-Party/dpdk/dpdk-16.07.orig/tools/dpdk-devbind.py
+++ /opt/Perforce/gtosatti_centos/E-XMS/CSA-Mainline/Third-Party/dpdk/dp
+++ dk-16.07/tools/dpdk-devbind.py
@@ -91,6 +91,9 @@
-u, --unbind:
Unbind a device (Equivalent to \"-b
On 22-Mar-18 1:41 PM, Tosatti, Giovanni wrote:
Hi all,
I'm new to this list.
I have a use case that required me to do a small enhancement to the
dpdk-devbind.py script.
In particular I found very useful to have a --restore option that will unbind
all devices currently bound to DPDK PMDs back to
5 matches
Mail list logo