From: David Marchand <david.marchand@redhat.com>
To: fwefew 4t4tg <7532yahoo@gmail.com>,
Marcin Wojtas <mw@semihalf.com>,
Michal Krawczyk <mk@semihalf.com>,
Shai Brandes <shaibran@amazon.com>,
Evgeny Schemeilin <evgenys@amazon.com>,
Igor Chauskin <igorch@amazon.com>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] AWS i3.metal and IOMMU
Date: Wed, 27 Oct 2021 08:46:05 +0200 [thread overview]
Message-ID: <CAJFAV8zgBX6jJ5h5FTKsE6qHoT_9wx1N4H6-cn+0VSQAV7uVvA@mail.gmail.com> (raw)
In-Reply-To: <CA+Tq66V2HkBPMZ+ikZT7k8ASvaP3RHEiPpWDKv6p+04+5xZ9Kg@mail.gmail.com>
On Wed, Oct 27, 2021 at 2:55 AM fwefew 4t4tg <7532yahoo@gmail.com> wrote:
>
> As per https://doc.dpdk.org/guides/nics/ena.html section 17.9
> enabling IOMMU on an AWS i3 metal instance is as simple as adding "iommu=1
> intel_iommu=on" to /etc/default/grub, update-grub, and reboot.
>
> I can't get this to work. Once done, I cannot ssh back into the instance;
> EC2 console can't get good status checks. It has to be terminated. My
> config:
>
> * Ubuntu 20.04 LTS x86 64-bit stock AWS AMI
> * i3.metal (spot)
>
> But more importantly: if one has provisioned a i3.metal instance, why
> enable IOMMU at all? Can't one just run vfio-pci in
> enable_unsafe_noiommu_mode?
>
> Even if IOMMU runs in enable_unsafe_noiommu_mode, I'd like to reconfirm the
> steps to make DPDK work on an AWS i3.metal instance. My steps are:
>
> * git clone https://github.com/amzn/amzn-drivers.git
> * git clone git://dpdk.org/dpdk and checkout tag 'v19.11-rc4'
> * in dpdk git am in the patches from amzn-drivers 19.11 userspace dir
> * build dpdk with: make install T=x86_64-native-linuxapp-gcc
> DESTDIR=/home/ubuntu/local
> * then follow the instructions at
> https://github.com/amzn/amzn-drivers/tree/master/userspace/dpdk/enav2-vfio-patch
> to build and install an updated vfio kernel module
>
> Is that complete and correct?
- Let's ask the ENA DPDK maintainers.
They should know best.
- While at it, what is the status of upstreaming this write combined
support in vfio?
I found a RFC from 2017, and did not find anything else.
We are trying to stick to upstream support, so mentioning in DPDK a
non upstream kernel patch is not cool.
--
David Marchand
prev parent reply other threads:[~2021-10-27 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 0:55 fwefew 4t4tg
2021-10-27 6:46 ` David Marchand [this message]
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=CAJFAV8zgBX6jJ5h5FTKsE6qHoT_9wx1N4H6-cn+0VSQAV7uVvA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=7532yahoo@gmail.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=ferruh.yigit@intel.com \
--cc=igorch@amazon.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.com \
--cc=shaibran@amazon.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).