From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>, <dev@dpdk.org>,
<jianbo.liu@linaro.org>, <santosh.shukla@caviumnetworks.com>,
<thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCHv3 1/2] config/armv8a: disable igb_uio
Date: Wed, 11 May 2016 22:32:16 +0530 [thread overview]
Message-ID: <20160511170215.GA1637@localhost.localdomain> (raw)
In-Reply-To: <20160511082259.42905f98@xeon-e3>
On Wed, May 11, 2016 at 08:22:59AM -0700, Stephen Hemminger wrote:
> On Wed, 11 May 2016 19:17:58 +0530
> Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
>
> > IGB_UIO not supported for arm64 arch in kernel so disable.
> >
> > Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> > Reviewed-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
>
> Really, I have use IGB_UIO on ARM64
May I know what is the technical use case for igb_uio on arm64
which cannot be addressed through vfio or vfioionommu.
next prev parent reply other threads:[~2016-05-11 17:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 13:47 Hemant Agrawal
2016-05-11 13:47 ` [dpdk-dev] [PATCHv3 2/2] mk: Introduce NXP dpaa2 architecture based on armv8-a Hemant Agrawal
2016-05-11 15:22 ` [dpdk-dev] [PATCHv3 1/2] config/armv8a: disable igb_uio Stephen Hemminger
2016-05-11 16:57 ` Santosh Shukla
2016-05-11 17:02 ` Jerin Jacob [this message]
2016-05-11 18:25 ` Stephen Hemminger
2016-05-12 2:01 ` Jianbo Liu
2016-05-12 3:17 ` Santosh Shukla
2016-05-12 3:42 ` Jianbo Liu
2016-05-12 5:06 ` Santosh Shukla
2016-05-12 5:54 ` Jianbo Liu
2016-05-12 8:57 ` Santosh Shukla
2016-05-12 9:52 ` Jianbo Liu
2016-05-12 10:31 ` Santosh Shukla
2016-05-13 1:43 ` Jianbo Liu
2016-05-13 3:37 ` Hemant Agrawal
2016-05-13 7:47 ` Jerin Jacob
2016-05-13 10:09 ` Jianbo Liu
2016-05-12 3:00 ` Jerin Jacob
2016-05-13 12:50 ` Thomas Monjalon
2016-05-13 13:11 ` Santosh Shukla
2016-05-18 14:28 ` Thomas Monjalon
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=20160511170215.GA1637@localhost.localdomain \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jianbo.liu@linaro.org \
--cc=santosh.shukla@caviumnetworks.com \
--cc=stephen@networkplumber.org \
--cc=thomas.monjalon@6wind.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).