DPDK usage discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Gregory Etelson <gregory@weka.io>, dev@dpdk.org, users@dpdk.org
Subject: Re: [dpdk-users] IGB_UIO: PCI Resources Management
Date: Thu, 12 Jan 2017 11:55:44 +0000	[thread overview]
Message-ID: <608e7dfd-5226-3e30-f43b-0fbe01aee16a@intel.com> (raw)
In-Reply-To: <3355891.l3I590SjcV@polaris>

On 12/9/2016 8:54 AM, Gregory Etelson wrote:
> Hello,
> 
> IGB_UIO driver does not close port PCI activities after DPDK process exits.
> DPDK API provides rte_eth_dev_close() to manage port PCI,
> but it can be skipped if process receives SIGKILL signal

I guess I understand the problem.

> The patches below provide IGB_UIO release callback and IXGBEVF release function

But adding ixgbe specific code into igb_uio may not be good idea.
Can be anything done one upper layer, pci layer, generic to all drivers?

> With the patches, each time DPDK process terminates,
> UIO release callback will trigger port PCI close.
> On the down side, patched IGB_UIO can be bound to a single adapter type
> 
> Regards,
> Gregory

<...>

  reply	other threads:[~2017-01-12 11:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09  8:54 Gregory Etelson
2017-01-12 11:55 ` Ferruh Yigit [this message]
2017-01-12 12:12   ` [dpdk-users] [dpdk-dev] " Alejandro Lucero
2017-01-12 12:22     ` Ferruh Yigit
2017-01-12 12:58       ` Alejandro Lucero
2017-01-13  1:51       ` Tan, Jianfeng
2017-01-13  2:04         ` Ferruh Yigit
2017-01-13  5:33           ` Tan, Jianfeng
2017-01-13 11:10             ` Alejandro Lucero
2017-01-19 16:36               ` Ferruh Yigit
2017-01-19 20:33                 ` Alejandro Lucero
2017-01-19 15:59             ` Ferruh Yigit
2017-01-19 16:09               ` George Prekas
2017-01-20  5:09               ` Tan, Jianfeng

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=608e7dfd-5226-3e30-f43b-0fbe01aee16a@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=gregory@weka.io \
    --cc=users@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).