From: Aaron Conole <aconole@redhat.com>
To: Panu Matilainen <pmatilai@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Permanently binding NIC ports with DPDK drivers
Date: Fri, 13 Nov 2015 09:42:00 -0500 [thread overview]
Message-ID: <f7tegfukll3.fsf@aconole.bos.csb> (raw)
In-Reply-To: <56448CB5.8070102@redhat.com> (Panu Matilainen's message of "Thu, 12 Nov 2015 14:57:25 +0200")
Panu Matilainen <pmatilai@redhat.com> writes:
> On 11/11/2015 06:28 PM, Bruce Richardson wrote:
>> 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
>>>
>>
>> Hi Francesco,
>>
>> 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.
>> For example, a couple of lines in an rc.local script can reapply the
>> bindings at
>> boot for you. I'm sure others can suggest other ways of having the
>> same effect,
>> for example, there may be a way to automatically do this using udev or systemd
>> or some such package.
>
> I've been looking into this recently, here's what I have so far:
> http://laiskiainen.org/git/?p=driverctl.git
>
I've been using this recently, on my systems.
+1 for driverctl :-)
next prev parent reply other threads:[~2015-11-13 14:42 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
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 [this message]
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=f7tegfukll3.fsf@aconole.bos.csb \
--to=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=pmatilai@redhat.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).