DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Tone Zhang (Arm Technology China)" <Tone.Zhang@arm.com>
To: Luca Boccassi <bluca@debian.org>,
	Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>,
	"roszenrami@gmail.com" <roszenrami@gmail.com>,
	Stephen Hemminger <stephen@networkplumber.org>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: Clarify IOMMU usage with "uio_pci_generic" kernel module
Date: Fri, 21 Sep 2018 02:39:29 +0000	[thread overview]
Message-ID: <AM0PR08MB3409F34274338A5DA2CF68D58F120@AM0PR08MB3409.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <1537358068.10481.22.camel@debian.org>

Hi Luca and Bruce,

I appreciate for the comments. I ran more test cases in my test bed, and I will update the patch and push v4 soon.

Thanks a lot for your help!

Br,
Tone

-----Original Message-----
From: Luca Boccassi <bluca@debian.org> 
Sent: Wednesday, September 19, 2018 7:54 PM
To: Bruce Richardson <bruce.richardson@intel.com>; Tone Zhang (Arm Technology China) <Tone.Zhang@arm.com>
Cc: dev@dpdk.org; Gavin Hu (Arm Technology China) <Gavin.Hu@arm.com>; roszenrami@gmail.com; Stephen Hemminger <stephen@networkplumber.org>; nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: Clarify IOMMU usage with "uio_pci_generic" kernel module

On Wed, 2018-09-19 at 12:33 +0100, Bruce Richardson wrote:
> On Wed, Sep 19, 2018 at 07:44:36AM +0000, Tone Zhang (Arm Technology
> China) wrote:
> > Hello Bruce, Luca, Rami and Stephen,
> > 
> > Could you please help to review the change?
> > 
> > Any comments are welcome.
> > 
> > Thanks a lot!
> > 
> > Br,
> > Tone
> > 
> > -----Original Message-----
> > From: dev <dev-bounces@dpdk.org> On Behalf Of tone.zhang
> > Sent: Wednesday, September 5, 2018 1:18 PM
> > To: dev@dpdk.org
> > Cc: Gavin Hu (Arm Technology China) <Gavin.Hu@arm.com>; bruce.richa 
> > rdson@intel.com; bluca@debian.org; roszenrami@gmail.com; nd <nd@arm 
> > .com>
> > Subject: [dpdk-dev] [PATCH v3] doc: Clarify IOMMU usage with 
> > "uio_pci_generic" kernel module
> > 
> > If the devices used for DPDK are bound to the "uio_pci_generic"
> > kernel module, the IOMMU should be disabled in order not to break 
> > the IO transmission because of the virtual / physical address 
> > mapping.
> > 
> > The patch clarifies the IOMMU configurations on both x86_64 and
> > arm64 systems.
> > 
> > Signed-off-by: tone.zhang <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..b46fc6a 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`` kernel module rather than ``igb_uio`` or 
> > ``uio_pci_generic``.
> >     For more details see :ref:`linux_gsg_binding_kernel` below.
> >  
> > +.. note::
> > +
> > +   If the devices used for DPDK are bound to the
> > ``uio_pci_generic`` kernel module,
> > +   please make sure that the IOMMU is disabled. One can add
> > ``intel_iommu=off`` or
> > +   ``intel_iommu=pt`` or ``amd_iommu=off`` in GRUB command line on
> > x86_64 systems,
> > +   or add ``iommu.passthrough=1`` on arm64 system.
> > +
> 
> I'm not really an expert in these IOMMU commands, but for the 
> passthrough option on my systems, I've always used "intel_iommu=on 
> iommu=pt", rather than "intel_iommu=pt". Can someone confirm that the 
> latter works ok, as documented here?
> 
> /Bruce

Whops you are right, just checked and we use iommu=pt

--
Kind regards,
Luca Boccassi

  reply	other threads:[~2018-09-21  2:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04  8:59 [dpdk-dev] [PATCH] doc: Clarify IOMMU usage with "uio-pci" " 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)
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) [this message]
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=AM0PR08MB3409F34274338A5DA2CF68D58F120@AM0PR08MB3409.eurprd08.prod.outlook.com \
    --to=tone.zhang@arm.com \
    --cc=Gavin.Hu@arm.com \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=nd@arm.com \
    --cc=roszenrami@gmail.com \
    --cc=stephen@networkplumber.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).