From: Stephen Hemminger <stephen@networkplumber.org>
To: "Zhou, Danny" <danny.zhou@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH 0/2] fix UIO support broken by 2.0
Date: Wed, 15 Apr 2015 09:34:20 -0700 [thread overview]
Message-ID: <20150415093420.6fc93b76@urahara> (raw)
In-Reply-To: <DFDF335405C17848924A094BC35766CF0AB5C943@SHSMSX104.ccr.corp.intel.com>
Here is the correct way to fix it (even if it maybe hard to accept).
I think the most technically correct way to handle this is to fix
UIO driver in kernel to do the IRQ management according to the
API that was already described in the kernel documentation.
Then have the DPDK EAL use the IRQ management API.
This maybe hard for Enterprise distributions to accept, but it is
the right technical solution.
next prev parent reply other threads:[~2015-04-15 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 1:06 [dpdk-dev] UIO pci-generic support broke igb_uio Stephen Hemminger
2015-04-15 7:19 ` Zhou, Danny
2015-04-15 15:57 ` Stephen Hemminger
2015-04-15 16:34 ` Stephen Hemminger [this message]
2015-04-15 16:36 ` [dpdk-dev] [PATCH 1/2 kernel] uio: add irq control support to uio_pci_generic Stephen Hemminger
2015-04-15 16:38 ` [dpdk-dev] [PATCH 2/2 dpdk] uio: fix pci generic driver breakage Stephen Hemminger
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=20150415093420.6fc93b76@urahara \
--to=stephen@networkplumber.org \
--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).