From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: "Stojaczyk, DariuszX" <dariuszx.stojaczyk@intel.com>
Cc: dev <dev@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] memory: do not use base-virtaddr in secondary processes
Date: Mon, 18 Jun 2018 20:33:14 +0100 [thread overview]
Message-ID: <CAD+H993g6CVaP0B4XZg=mMbrmiZzrBW6ymR8eDM4FPwtcU3FZg@mail.gmail.com> (raw)
In-Reply-To: <FBE7E039FA50BF47A673AD0BD3CD56A8461605C7@HASMSX105.ger.corp.intel.com>
On Mon, Jun 18, 2018 at 8:03 PM, Stojaczyk, DariuszX <
dariuszx.stojaczyk@intel.com> wrote:
>
> > -----Original Message-----
> > From: Alejandro Lucero [mailto:alejandro.lucero@netronome.com]
> > Sent: Monday, June 18, 2018 7:22 PM
> >
> > Should not be better to handle these allocations being aware about the
> > problem for secondary processes?
> >
> > I do not know exactly what are the (other) reasons behind base-virtaddr,
> > but it turns out NFP requires this to be used when DPDK apps executed
> > by non-root users.
> >
> > I'm working on a RFC for handling our specific case, that could also be
> > required for other devices, and this change would make the NFP unusable
> > for the secondary processes.
> >
>
> The only place base-virtaddr is used in secondary processes in DPDK 18.05
> is this shadow memseg mapping, which shouldn't really need to be accessed
> by anyone else than DPDK EAL.
Yes, I'm aware this is EAL code.
Can you point me out to an NFP guide or some code that describes this in
> more detail?
>
As I said, I'm working on a RFC. I will send something shortly. But I could
give you an advance: the hugepages needs to be mapped below certain virtual
address, 1TB, and I'm afraid that includes the primary and also the
secondary processes. At least if any process can send or receive packets
to/from a NFP.
>
> If we're talking about base-virtaddr for hugepages, then that's always
> inherited from the primary process, regardless of what base-virtaddr is
> supplied to the secondary.
>
>
But, is not your patch avoiding to use that base-virtaddr for secondary
processes?
> Regards!
> D.
>
next prev parent reply other threads:[~2018-06-18 19:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 19:53 [dpdk-stable] " Dariusz Stojaczyk
2018-06-18 17:21 ` [dpdk-stable] [dpdk-dev] " Alejandro Lucero
2018-06-18 19:03 ` Stojaczyk, DariuszX
2018-06-18 19:33 ` Alejandro Lucero [this message]
2018-06-18 20:12 ` Stojaczyk, DariuszX
2018-06-19 9:24 ` Burakov, Anatoly
2018-06-19 10:23 ` Alejandro Lucero
2018-06-19 10:27 ` Burakov, Anatoly
2018-06-19 11:48 ` Alejandro Lucero
2018-06-19 9:21 ` [dpdk-stable] " Burakov, Anatoly
2018-07-12 22:08 ` [dpdk-stable] [dpdk-dev] " 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='CAD+H993g6CVaP0B4XZg=mMbrmiZzrBW6ymR8eDM4FPwtcU3FZg@mail.gmail.com' \
--to=alejandro.lucero@netronome.com \
--cc=anatoly.burakov@intel.com \
--cc=dariuszx.stojaczyk@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.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).