From: Matthew Hall <mhall@mhcomputing.net>
To: "Montorsi, Francesco" <fmontorsi@empirix.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Permanently binding NIC ports with DPDK drivers
Date: Wed, 11 Nov 2015 14:01:21 -0500 [thread overview]
Message-ID: <20151111190121.GB18270@mhcomputing.net> (raw)
In-Reply-To: <964049bfb9054699a2e4520c6758a7ee@bilemail1.empirix.com>
In my development environment I set up an at-boot provisioning script that
does it. I recommend using scripts and not shelling out from C code. ;)
On Wed, Nov 11, 2015 at 04:13:01PM +0000, Montorsi, Francesco wrote:
> Hi,
> Is there a way to permanently (i.e., have the configuration automatically applied after reboot) bind a NIC port to DPDK?
>
> In case there's none, I'm thinking to save in my software a list of the NIC ports chosen by the user for use with DPDK and then, upon software startup to just do
> for (int i=0; i < ...; i++)
> system("dpdk_nic_bind.py --bind=igb_uio " + PCI_device_chosen[i]);
> Do you see any problem with that?
>
> Thanks!
> Francesco Montorsi
>
next prev parent reply other threads:[~2015-11-11 19:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 16:13 Permanently binding NIC ports with DPDK drivers Montorsi, Francesco
2015-11-11 16:28 ` Bruce Richardson
2015-11-11 16:59 ` Montorsi, Francesco
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 [this message]
2015-11-12 0:14 ` Mcnamara, John
2015-11-13 11:48 ` Montorsi, Francesco
2015-11-13 12:24 ` Panu Matilainen
-- strict thread matches above, loose matches on Subject: below --
2016-08-25 4:57 Keren Hochman
2016-08-25 11:01 ` Ferruh Yigit
2016-08-25 11:53 ` Panu Matilainen
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=20151111190121.GB18270@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=fmontorsi@empirix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.