DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier Deme <odeme@druidsoftware.com>
To: "Zhou, Danny" <danny.zhou@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] KNI automatic IP configuration
Date: Sat, 4 Apr 2015 18:02:54 +0100	[thread overview]
Message-ID: <197B7176-9E88-4E24-9343-68E597CB143F@druidsoftware.com> (raw)
In-Reply-To: <DFDF335405C17848924A094BC35766CF0AB44326@SHSMSX104.ccr.corp.intel.com>

Currently I’m using the e1000 PMD driver.

Thanks,
Olivier.

> On 4 Apr 2015, at 12:51, Zhou, Danny <danny.zhou@intel.com> wrote:
> 
> Which NIC device are you using now?
> 
> KNI does not provide Ethtool support for all NICs supported by the Poll-Mode Drivers.
> 
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier Deme
>> Sent: Friday, April 03, 2015 10:03 PM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] KNI automatic IP configuration
>> 
>> Hi all,
>> 
>> Is it possible on Linux to get the Linux network manager to automatically configure a KNI virtual network interface as soon as it
>> comes up?
>> I haven’t been able to get Fedora to apply the configuration under /etc/sysconfig/network-scripts/ifcfg-veth0 file upon starting
>> my DPDK application.
>> 
>> Executing ifup veth0 manually works but somehow the fedora network manager seems to have an issue to apply the if cfg config
>> automatically.
>> In the system logs I can see something along the lines “kni doesn’t support ethtool”. Is this related?
>> 
>> I also tried ifplugd but without success.
>> 
>> Many thanks for your help,
>> 
>> Olivier.
> 

  reply	other threads:[~2015-04-04 17:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 14:02 Olivier Deme
2015-04-04 11:51 ` Zhou, Danny
2015-04-04 17:02   ` Olivier Deme [this message]
2015-04-05  1:08     ` Zhou, Danny
2015-04-16 11:16       ` Olivier Deme

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=197B7176-9E88-4E24-9343-68E597CB143F@druidsoftware.com \
    --to=odeme@druidsoftware.com \
    --cc=danny.zhou@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).