On Wed, 11 Nov 2015 16:59:14 +0000 "Montorsi, Francesco" <fmontorsi at empirix.com> wrote:
> Hi Bruce, > > > -----Original Message----- > > From: Bruce Richardson [mailto:bruce.richardson at intel.com] > > I'm not aware of any way to make the bindings permanent across reboots. > > What you have suggested will work, but there are probably better ways to > > do the same thing. > > I agree... let's see if somebody else has suggestions :) > > In any case my idea is to make my software as much independent as possible > from troubles with future HW and future DPDK versions. A way to do that would > be to leave all the bind steps and intelligence inside the dpdk_nic_bind.py > script and just use that (since it will be probably always up to date and > correct). My only concern is that (reading the python code) dpdk_nic_bind.py > script does not return with an error code != 0 if something bad happens > during binding... maybe it may be worth doing such a small change... > > Just my 2 cents, > Francesco > > > > I would recommend using PCI id's and not depending in anyway on port. If you want, I can submit a patch to add derive the systemd/udev compatiable name from existing DPDK port.
