DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Junguk Cho <jmanbal@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] How to get "--base-virtaddr" when using DPDK
Date: Fri, 16 Jun 2017 09:54:45 +0100	[thread overview]
Message-ID: <20170616085445.GA82628@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <CAMNaBtNLwuEehxSjC6KG7tbupyrDJii3JDXpmX9afgZOrUeO8A@mail.gmail.com>

On Thu, Jun 15, 2017 at 12:00:16PM -0600, Junguk Cho wrote:
> Hi,
> 
> I have the same situation which is explained here (
> https://github.com/collectd/collectd/issues/2284).
> 
> So, I would like to try "--base-virtaddr" option.
> I tried to use "struct rte_memseg *m = rte_eal_get_physmem_layout()" option
> based on (http://dpdk.org/doc/api/structrte__memseg.html).
> However, it always  returns different number.
> 
> How do I get virtual address value to use it as an input of "base-viraddr"?
> 
Hi,

there is no one way to get a virtual address to pass in here - if you
are aware of some suitable values just pass them directly. What I have
done in the past in a multi-process system, is to run the primary
normaly, and then when running the failing secondary turn up the log
level so I can see the mapped addresses before it fails. Then I record
the starting address that the secondary uses, and re-run the primary
passing that in as the base-virtaddr hint.

Regards,
/Bruce

      reply	other threads:[~2017-06-16  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15 18:00 Junguk Cho
2017-06-16  8:54 ` Bruce Richardson [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=20170616085445.GA82628@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jmanbal@gmail.com \
    --cc=users@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).