DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Venumadhav Josyula <vjosyula@gmail.com>, users <users@dpdk.org>,
	dev@dpdk.org
Subject: Re: [dpdk-dev] Using rte_lpm as standalone library w/o mempools or dpdk infra
Date: Fri, 3 Apr 2020 09:55:14 +0100	[thread overview]
Message-ID: <fbf3a7ff-614f-9d73-2e63-89ca1eb56658@intel.com> (raw)
In-Reply-To: <CA+i0PGWGvjdiHn4e2uMFOQsusALJX7DPQB5W6rygAfFu+cekmQ@mail.gmail.com>

On 02-Apr-20 1:51 PM, Venumadhav Josyula wrote:
> Hi All,
> 
> Idea is following
>     - create lpm in one process where only rte_lpm and bare minimum is
> acessible. Addition into this table will also happen in this process
> context.
>     - Now in the packet processing context based ip of packet the lookup
> will happen in the lpm created.
> 
> Is above possible. Please task / Process in which lpm created or lpm
> entries added, does not do anything with respect to rte_eal.
> 
> Any pointers, will really be appreciated.
> 
> Cheers,
> Venu
> 

It is certainly possible to do that in principle, but it is not possible 
with current implementation. The LPM library relies on rte_malloc() for 
initialization, and that in turn relies on EAL structures being 
initialized, and DPDK hugepage memory being available.

If your concern is specifically to not use DPDK-allocated hugepage 
memory but use one that your application controls, it is possible to not 
use built-in DPDK memory and lessen the impact of DPDK initialization on 
the system with a few tricks (run in --in-memory and --no-huge mode with 
a tiny amount of memory, and use external memory API to create data 
structures in a memory you control), but you can't avoid it entirely.

-- 
Thanks,
Anatoly

      reply	other threads:[~2020-04-03  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 12:51 Venumadhav Josyula
2020-04-03  8:55 ` Burakov, Anatoly [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=fbf3a7ff-614f-9d73-2e63-89ca1eb56658@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=users@dpdk.org \
    --cc=vjosyula@gmail.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).