From: Jianfeng Tan <jianfeng.tan@intel.com>
To: dev@dpdk.org
Cc: santosh.shukla@caviumnetworks.com,
sergio.gonzalez.monroy@intel.com, thomas@monjalon.net,
ferruh.yigit@intel.com, Jianfeng Tan <jianfeng.tan@intel.com>
Subject: [dpdk-dev] [PATCH 0/2] enable 4KB + VFIO-PCI
Date: Wed, 11 Oct 2017 10:33:46 +0000 [thread overview]
Message-ID: <1507718028-12943-1-git-send-email-jianfeng.tan@intel.com> (raw)
Patch 1: Use VA as IOVA if IOVA mode is enabled.
Patch 2: Enable IOVA mode for the PMDs for Intel NICs.
How to test:
$ (bind nic to vfio-pci)
$ testpmd -c 0x3 -n 4 -m 2048 --no-huge -- -i --no-numa
Jianfeng Tan (2):
eal: honor IOVA mode for no-huge case
net: enable IOVA mode for PMDs
drivers/net/e1000/em_ethdev.c | 3 ++-
drivers/net/e1000/igb_ethdev.c | 5 +++--
drivers/net/fm10k/fm10k_ethdev.c | 3 ++-
drivers/net/i40e/i40e_ethdev.c | 3 ++-
drivers/net/i40e/i40e_ethdev_vf.c | 2 +-
drivers/net/ixgbe/ixgbe_ethdev.c | 5 +++--
lib/librte_eal/linuxapp/eal/eal_memory.c | 5 ++++-
7 files changed, 17 insertions(+), 9 deletions(-)
--
2.7.4
next reply other threads:[~2017-10-11 10:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 10:33 Jianfeng Tan [this message]
2017-10-11 10:33 ` [dpdk-dev] [PATCH 1/2] eal: honor IOVA mode for no-huge case Jianfeng Tan
2017-10-11 11:27 ` Burakov, Anatoly
2017-10-11 11:30 ` santosh
2017-10-31 21:49 ` Ferruh Yigit
2017-10-31 22:37 ` Ferruh Yigit
2017-11-01 1:10 ` Ferruh Yigit
2017-10-11 10:33 ` [dpdk-dev] [PATCH 2/2] net: enable IOVA mode for PMDs Jianfeng Tan
2017-10-11 10:43 ` Burakov, Anatoly
2017-10-11 10:56 ` Tan, Jianfeng
2017-10-11 11:30 ` Burakov, Anatoly
2017-10-11 11:33 ` santosh
2018-01-05 10:32 ` Maxime Coquelin
2018-01-05 12:04 ` Maxime Coquelin
2018-01-05 12:10 ` santosh
2018-01-05 12:57 ` Maxime Coquelin
2017-10-11 10:47 ` [dpdk-dev] [PATCH 0/2] enable 4KB + VFIO-PCI Burakov, Anatoly
2017-10-11 10:50 ` Thomas Monjalon
2017-10-12 19:57 ` Ferruh Yigit
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=1507718028-12943-1-git-send-email-jianfeng.tan@intel.com \
--to=jianfeng.tan@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=santosh.shukla@caviumnetworks.com \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=thomas@monjalon.net \
/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).