From: Venumadhav Josyula <vjosyula@gmail.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
users@dpdk.org, dev@dpdk.org,
Venumadhav Josyula <vjosyula@parallelwireless.com>
Subject: Re: [dpdk-users] [dpdk-dev] time taken for allocation of mempool.
Date: Mon, 18 Nov 2019 22:13:24 +0530 [thread overview]
Message-ID: <CA+i0PGXRjnFPQkt2+R83Lf_2+xp9rhzgsa+yxqj07-p9=oihwA@mail.gmail.com> (raw)
In-Reply-To: <c935606c-0549-349a-1206-5c9b2ef6e1d7@intel.com>
Hi Anatoly,
After using iova-mode=va, i see my ports are not getting detected ? I
thought it's working but I see following problem
what could be the problem?
i) I see allocation is faster
ii) But my ports are not getting detected
I take my word back that it entirely working..
Thanks,
Regards,
Venu
On Thu, 14 Nov 2019 at 15:27, Burakov, Anatoly <anatoly.burakov@intel.com>
wrote:
> On 14-Nov-19 9:50 AM, Venumadhav Josyula wrote:
> > Hi Anatoly,
> >
> > Thanks for quick response. We want to understand, if there will be
> > performance implications because of iova-mode being va. We want to
> > understand, specifically in terms following
> >
> > * cache misses
> > * Branch misses etc
> > * translation of va addr -> phy addr when packet is receieved
> >
>
> There will be no impact whatsoever. You mentioned that you were already
> using VFIO, so you were already making use of IOMMU*. Cache/branch
> misses are independent of IOVA layout, and translations are done by the
> hardware (in either IOVA as PA or IOVA as VA case - IOMMU doesn't care
> what you program it with, it still does the translation, even if it's a
> 1:1 IOVA-to-PA mapping), so there is nothing that can cause degradation.
>
> In fact, under some circumstances, using IOVA as VA mode can be used to
> get performance /gains/, because the code can take advantage of the fact
> that there are large IOVA-contiguous segments and no page-by-page
> allocations. Some drivers (IIRC octeontx mempool?) even refuse to work
> in IOVA as PA mode due to huge overheads of page-by-page buffer offset
> tracking.
>
> TL;DR you'll be fine :)
>
> * Using an IOMMU can /theoretically/ affect performance due to hardware
> IOVA->PA translation and IOTLB cache misses. In practice, i have never
> been able to observe /any/ effect whatsoever on performance when using
> IOMMU vs. without using IOMMU, so this appears to not be a concern /in
> practice/.
>
> > Thanks and regards
> > Venu
> >
> > On Thu, 14 Nov 2019 at 15:14, Burakov, Anatoly
> > <anatoly.burakov@intel.com <mailto:anatoly.burakov@intel.com>> wrote:
> >
> > On 13-Nov-19 9:01 PM, Venumadhav Josyula wrote:
> > > Hi Anatoly,
> > >
> > > By default w/o specifying --iova-mode option is iova-mode=pa by
> > default ?
> > >
> > > Thanks
> > > Venu
> > >
> >
> > In 18.11, there is a very specific set of circumstances that will
> > default to IOVA as VA mode. Future releases have become more
> > aggressive,
> > to the point of IOVA as VA mode being the default unless asked
> > otherwise. So yes, it is highly likely that in your case, IOVA as PA
> is
> > picked as the default.
> >
> > --
> > Thanks,
> > Anatoly
> >
>
>
> --
> Thanks,
> Anatoly
>
next prev parent reply other threads:[~2019-11-18 16:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 5:07 [dpdk-users] " Venumadhav Josyula
2019-11-13 5:12 ` Venumadhav Josyula
2019-11-13 8:32 ` [dpdk-users] [dpdk-dev] " Olivier Matz
2019-11-13 9:11 ` Venumadhav Josyula
2019-11-13 9:30 ` Olivier Matz
2019-11-13 9:19 ` Bruce Richardson
2019-11-13 17:26 ` Burakov, Anatoly
2019-11-13 21:01 ` Venumadhav Josyula
2019-11-14 9:44 ` Burakov, Anatoly
2019-11-14 9:50 ` Venumadhav Josyula
2019-11-14 9:57 ` Burakov, Anatoly
2019-11-18 16:43 ` Venumadhav Josyula [this message]
2019-12-06 10:47 ` Burakov, Anatoly
2019-12-06 10:49 ` Venumadhav Josyula
2019-11-14 8:12 ` Venumadhav Josyula
2019-11-14 9:49 ` Burakov, Anatoly
2019-11-14 9:53 ` Venumadhav Josyula
2019-11-18 16:45 ` [dpdk-users] " Venumadhav Josyula
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='CA+i0PGXRjnFPQkt2+R83Lf_2+xp9rhzgsa+yxqj07-p9=oihwA@mail.gmail.com' \
--to=vjosyula@gmail.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=users@dpdk.org \
--cc=vjosyula@parallelwireless.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).