From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Alejandro Lucero <alejandro.lucero@netronome.com>,
"dariusz.stojaczyk@intel.com" <dariusz.stojaczyk@intel.com>,
dev <dev@dpdk.org>, "Shukla, Santosh" <Santosh.Shukla@cavium.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"chas3@att.com" <chas3@att.com>
Subject: Re: [PATCH] pci/linux: use RTE_IOVA_VA whenever possible
Date: Thu, 11 Oct 2018 10:47:12 +0000 [thread overview]
Message-ID: <20181011104702.GA18152@jerin> (raw)
In-Reply-To: <93d12b45-d0a9-ab28-5ead-c3424067a062@intel.com>
-----Original Message-----
> Date: Thu, 11 Oct 2018 11:26:05 +0100
> From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
> To: Alejandro Lucero <alejandro.lucero@netronome.com>,
> dariusz.stojaczyk@intel.com
> CC: dev <dev@dpdk.org>, Santosh Shukla <santosh.shukla@caviumnetworks.com>,
> Hemant Agrawal <hemant.agrawal@nxp.com>, Jerin Jacob
> <jerin.jacob@caviumnetworks.com>, Maxime Coquelin
> <maxime.coquelin@redhat.com>, chas3@att.com
> Subject: Re: [dpdk-dev] [PATCH] pci/linux: use RTE_IOVA_VA whenever possible
> User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
> Thunderbird/52.9.1
>
>
> On 11-Oct-18 11:00 AM, Alejandro Lucero wrote:
> > On Fri, Sep 7, 2018 at 3:55 PM Darek Stojaczyk <dariusz.stojaczyk@intel.com>
> > wrote:
> >
> > > This allows DPDK to use RTE_IOVA_VA with VFIO/UIO-bound PCI
> > > devices present on the system, but not attached to any
> > > rte_pci_driver at the time of init.
> > >
> > > So far we used RTE_IOVA_VA whenever there was at least one
> > > device attached to a driver with an RTE_PCI_DRV_IOVA_AS_VA flag,
> > > meaning that other drivers which didn't explicitly report such
> > > flag could have been forced to work in RTE_IOVA_VA as well.
> > >
> >
> > This is the opposite. Just one device not being able to use IOVA VA makes
> > all to use IOVA PA.
> >
> >
> > >
> > > This patch makes the RTE_PCI_DRV_IOVA_AS_VA explicitly a hint.
> > > If it's set, but RTE_IOVA_VA cannot be used, then EAL will print
> > > a proper warning.
> > >
> > > Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
> > > ---
> > > drivers/bus/pci/linux/pci.c | 11 +++++------
> > > 1 file changed, 5 insertions(+), 6 deletions(-)
> > >
> > > diff --git a/drivers/bus/pci/linux/pci.c b/drivers/bus/pci/linux/pci.c
> > > index 04648ac93..961e24024 100644
> > > --- a/drivers/bus/pci/linux/pci.c
> > > +++ b/drivers/bus/pci/linux/pci.c
> > > @@ -534,7 +534,7 @@ pci_one_device_bound_uio(void)
> > > * Any one of the device has iova as va
> > > */
> > > static inline int
> > > -pci_one_device_has_iova_va(void)
> > > +pci_one_device_want_iova_va(void)
> > > {
> > > struct rte_pci_device *dev = NULL;
> > > struct rte_pci_driver *drv = NULL;
> > > @@ -635,7 +635,7 @@ rte_pci_get_iommu_class(void)
> > > {
> > > bool is_bound;
> > > bool is_vfio_noiommu_enabled = true;
> > > - bool has_iova_va;
> > > + bool want_iova_va;
> > > bool is_bound_uio;
> > > bool iommu_no_va;
> > >
> > > @@ -643,7 +643,7 @@ rte_pci_get_iommu_class(void)
> > > if (!is_bound)
> > > return RTE_IOVA_DC;
> > >
> > > - has_iova_va = pci_one_device_has_iova_va();
> > > + want_iova_va = pci_one_device_want_iova_va();
> > > is_bound_uio = pci_one_device_bound_uio();
> > > iommu_no_va = !pci_devices_iommu_support_va();
> > > #ifdef VFIO_PRESENT
> > > @@ -651,11 +651,10 @@ rte_pci_get_iommu_class(void)
> > > true : false;
> > > #endif
> > >
> > > - if (has_iova_va && !is_bound_uio && !is_vfio_noiommu_enabled &&
> > > - !iommu_no_va)
> > > + if (!is_bound_uio && !is_vfio_noiommu_enabled && !iommu_no_va)
> > > return RTE_IOVA_VA;
> > >
> >
> > This is wrong. A device not able to work with IOVA VA will fail.
> >
> >
> > >
> > > - if (has_iova_va) {
> > > + if (want_iova_va) {
> > > RTE_LOG(WARNING, EAL, "Some devices want iova as va but pa
> > > will be used because.. ");
> > > if (is_vfio_noiommu_enabled)
> > > RTE_LOG(WARNING, EAL, "vfio-noiommu mode
> > > configured\n");
> > > --
> > > 2.17.1
> > >
> > >
> >
>
> For these cases, i think the explicit IOVA mode on command line should
> work better. If the device has not reported IOVA as VA capability, it is
> to be assumed unsupported.
Yes.
>
> --
> Thanks,
> Anatoly
next prev parent reply other threads:[~2018-10-11 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 14:53 [PATCH] pci/linux: use RTE_IOVA_VA whenever possible Darek Stojaczyk
2018-10-11 9:48 ` Thomas Monjalon
2018-10-11 10:00 ` Alejandro Lucero
2018-10-11 10:26 ` Burakov, Anatoly
2018-10-11 10:47 ` Jerin Jacob [this message]
2018-10-28 18:56 ` 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=20181011104702.GA18152@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=Santosh.Shukla@cavium.com \
--cc=alejandro.lucero@netronome.com \
--cc=anatoly.burakov@intel.com \
--cc=chas3@att.com \
--cc=dariusz.stojaczyk@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=maxime.coquelin@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.