DPDK patches and discussions
 help / color / mirror / Atom feed
From: Panu Matilainen <pmatilai@redhat.com>
To: "Montorsi, Francesco" <fmontorsi@empirix.com>,
	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: Fri, 13 Nov 2015 14:17:40 +0200	[thread overview]
Message-ID: <5645D4E4.4000903@redhat.com> (raw)
In-Reply-To: <8f345cadb32e443daf59127eeebe83c6@bilemail1.empirix.com>

On 11/13/2015 01:44 PM, Montorsi, Francesco wrote:
> Hi Panu,
>
>> -----Original Message-----
>> From: Panu Matilainen [mailto:pmatilai@redhat.com]
>> I've been looking into this recently, here's what I have so far:
>> http://laiskiainen.org/git/?p=driverctl.git
>>
> Thanks I tried the script (I just had to change /bin/sh into
> /bin/bash on first line) and it works fine on my Ubuntu 14.04.

Oops, fixed now. Thanks for pointing that out, the line between sh and 
bash is (too) blurry on Fedora & friends.

> Unfortunately I'm forced to run my sw on SLES 11.3 (which btw uses
> kernel 3.0.76 which I don't know if is compatible with VFIO) and there
> the output of "list-devices" is plain empty. I will try to look at
> what's happening...

list-devices currently only lists devices which support driver 
overriding[*], which is a relatively new kernel feature and would be 
missing from 3.0.76:
https://www.redhat.com/archives/libvir-list/2014-April/msg00222.html

It might well be possible to fall back to the "old style" bind system if 
the kernel doesn't support driver_override. I've no immediate plans to 
look into that but lets just say patches would at least be considered :)

	- Panu -

  reply	other threads:[~2015-11-13 12:17 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 [this message]
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=5645D4E4.4000903@redhat.com \
    --to=pmatilai@redhat.com \
    --cc=bruce.richardson@intel.com \
    --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 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).