DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Montorsi, Francesco" <fmontorsi@empirix.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Permanently binding NIC ports with DPDK drivers
Date: Wed, 11 Nov 2015 16:59:14 +0000	[thread overview]
Message-ID: <289cd55a3a7b498c974a083927fc81cc@bilemail1.empirix.com> (raw)
In-Reply-To: <20151111162853.GA38496@bricha3-MOBL3>

Hi Bruce,

> -----Original Message-----
> From: Bruce Richardson [mailto:bruce.richardson@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

  reply	other threads:[~2015-11-11 16:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 16:13 Montorsi, Francesco
2015-11-11 16:28 ` Bruce Richardson
2015-11-11 16:59   ` Montorsi, Francesco [this message]
2015-11-11 17:29     ` Stephen Hemminger
2015-11-12 12:57   ` Panu Matilainen
2015-11-13 11:44     ` Montorsi, Francesco
2015-11-13 12:17       ` Panu Matilainen
2015-11-13 14:42     ` Aaron Conole
2015-11-11 19:01 ` Matthew Hall
2015-11-12  0:14 ` Mcnamara, John
2015-11-13 11:48   ` Montorsi, Francesco
2015-11-13 12:24     ` Panu Matilainen
2016-08-25  4:57 Keren Hochman
2016-08-25 11:01 ` Ferruh Yigit

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=289cd55a3a7b498c974a083927fc81cc@bilemail1.empirix.com \
    --to=fmontorsi@empirix.com \
    --cc=bruce.richardson@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).