From: "Tone Zhang (Arm Technology China)" <Tone.Zhang@arm.com>
To: Rami Rosen <roszenrami@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] doc: Clarify IOMMU usage with "uio-pci" kernel module
Date: Wed, 5 Sep 2018 00:20:29 +0000 [thread overview]
Message-ID: <AM0PR08MB340928817C92238B5F1F8F7F8F020@AM0PR08MB3409.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAKoUArkeYcOR-F8vOOHOoA4updbuejX1e0pMzTNASmo2qsZWJg@mail.gmail.com>
Hi Rami,
Yes, I mean “uio_pci_generic” kernel module.
I will update the change accordingly.
Thanks.
Br,
Tone
From: Rami Rosen <roszenrami@gmail.com>
Sent: Wednesday, September 5, 2018 3:55 AM
To: Tone Zhang (Arm Technology China) <Tone.Zhang@arm.com>
Cc: dev@dpdk.org; nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] doc: Clarify IOMMU usage with "uio-pci" kernel module
Hi Tone,
>if the devices for used DPDK bound to the ``uio-pci`` kernel module, please make
The three kernel modules which can be used for DPDK binding are vfio-pci, uio_pci_generic and igb_uio. Don't you mean here uio_pci_generic ?
Regards,
Rami Rosen
בתאריך יום ג׳, 4 בספט׳ 2018, 11:59, מאת tone.z
When binding the devices used by DPDK to the "uio-pci" kernel module,
the IOMMU should be disabled in order not to break the
because of the virtual / physical address mapping.
The patch clarifies the IOMMU configuration on both x86_64 and arm64
systems.
Signed-off-by: tone.zhang <tone.zhang@arm.com<mailto:tone.zhang@arm.com>>
---
doc/guides/linux_gsg/linux_drivers.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/guides/linux_gsg/linux_drivers.rst b/doc/guides/linux_gsg/linux_drivers.rst
index 371a817..8f9ec8f 100644
--- a/doc/guides/linux_gsg/linux_drivers.rst
+++ b/doc/guides/linux_gsg/linux_drivers.rst
@@ -48,6 +48,13 @@ be loaded as shown below:
``vfio-pci``
2.7.4
next prev parent reply other threads:[~2018-09-05 0:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 8:59 tone.zhang
2018-09-04 9:16 ` Gavin Hu (Arm Technology China)
2018-09-04 10:06 ` Bruce Richardson
2018-09-04 10:15 ` Luca Boccassi
2018-09-04 10:25 ` Tone Zhang (Arm Technology China)
2018-09-04 19:55 ` Rami Rosen
2018-09-05 0:20 ` Tone Zhang (Arm Technology China) [this message]
2018-09-05 9:22 ` Stephen Hemminger
2018-09-05 9:49 ` Tone Zhang (Arm Technology China)
2018-09-05 4:39 ` [dpdk-dev] [PATCH v2] doc: Clarify IOMMU usage with "uio_pci_generic" " tone.zhang
2018-09-05 5:17 ` [dpdk-dev] [PATCH v3] " tone.zhang
2018-09-05 5:23 ` Gavin Hu (Arm Technology China)
2018-09-19 7:44 ` Tone Zhang (Arm Technology China)
2018-09-19 11:33 ` Bruce Richardson
2018-09-19 11:54 ` Luca Boccassi
2018-09-21 2:39 ` Tone Zhang (Arm Technology China)
2018-09-19 10:42 ` Luca Boccassi
2018-09-21 3:07 ` [dpdk-dev] [PATCH v4] " tone.zhang
2018-09-21 11:20 ` Bruce Richardson
2018-09-25 6:18 ` Tone Zhang (Arm Technology China)
2018-09-25 6:54 ` [dpdk-dev] [PATCH v5] " tone.zhang
2018-09-26 5:08 ` [dpdk-dev] [PATCH v6] " tone.zhang
2018-11-19 0:04 ` 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=AM0PR08MB340928817C92238B5F1F8F7F8F020@AM0PR08MB3409.eurprd08.prod.outlook.com \
--to=tone.zhang@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=roszenrami@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).