DPDK patches and discussions
 help / color / mirror / Atom feed
From: Remy Horton <remy.horton@intel.com>
To: Gopakumar Choorakkot Edakkunni <gopakumar.c.e@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] ethtool doesnt work on some interface after unbinding dpdk
Date: Mon, 18 Apr 2016 11:08:25 +0100	[thread overview]
Message-ID: <5714B219.7080202@intel.com> (raw)
In-Reply-To: <CABK1yFDVVMjBxiYFP6KzjODtsRc0H+scrvHJszYV_mhscXDpjQ@mail.gmail.com>


On 15/04/2016 23:56, Gopakumar Choorakkot Edakkunni wrote:
> This time the problem statement is more narrowed down.
>
> 1. dpdk is enabled on the interface, interfaces bound to igb_uio
> 3. kill the process using dpdk
> 3. rmmod rte_kni
> 4. rmmod igb_uio
> 5. bind interface to igb
> 6. ethtool, ifconfig up/down etc.. works for approximately 30 seconds,
> and then stops working

Hmm.. can you try that but with rte_kni left out completely? KNI hooks 
into the Linux network stack and think it at the least needs eliminating 
as a casual factor. Can you also try using uio_pci_generic rather than 
igb_uio?

Those aside, I'm suspecting driver issues, so seeing if I can get one of 
the driver test guys to have a look at this..


Regards,

..Remy

  reply	other threads:[~2016-04-18 10:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 14:48 Gopakumar Choorakkot Edakkunni
2016-04-14  7:15 ` Remy Horton
2016-04-14 19:25   ` Gopakumar Choorakkot Edakkunni
2016-04-15  7:50     ` Remy Horton
2016-04-15 17:38       ` Gopakumar Choorakkot Edakkunni
2016-04-15 19:31         ` Gopakumar Choorakkot Edakkunni
2016-04-15 22:56           ` Gopakumar Choorakkot Edakkunni
2016-04-18 10:08             ` Remy Horton [this message]
2016-04-30  1:23               ` Gopakumar Choorakkot Edakkunni

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=5714B219.7080202@intel.com \
    --to=remy.horton@intel.com \
    --cc=dev@dpdk.org \
    --cc=gopakumar.c.e@gmail.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).