DPDK usage discussions
 help / color / Atom feed
* [dpdk-users] Using rte_lpm as standalone library w/o mempools or dpdk infra
@ 2020-04-02 12:51 Venumadhav Josyula
  2020-04-03  8:55 ` [dpdk-users] [dpdk-dev] " Burakov, Anatoly
  0 siblings, 1 reply; 2+ messages in thread
From: Venumadhav Josyula @ 2020-04-02 12:51 UTC (permalink / raw)
  To: users, dev

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [dpdk-users] [dpdk-dev] Using rte_lpm as standalone library w/o mempools or dpdk infra
  2020-04-02 12:51 [dpdk-users] Using rte_lpm as standalone library w/o mempools or dpdk infra Venumadhav Josyula
@ 2020-04-03  8:55 ` " Burakov, Anatoly
  0 siblings, 0 replies; 2+ messages in thread
From: Burakov, Anatoly @ 2020-04-03  8:55 UTC (permalink / raw)
  To: Venumadhav Josyula, users, dev

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-02 12:51 [dpdk-users] Using rte_lpm as standalone library w/o mempools or dpdk infra Venumadhav Josyula
2020-04-03  8:55 ` [dpdk-users] [dpdk-dev] " Burakov, Anatoly

DPDK usage discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/ public-inbox