DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
	dev@dpdk.org, Nikita Kozlov <nikita@gandi.net>
Subject: Re: [dpdk-dev] LPM6 next hop size
Date: Wed, 21 Sep 2016 16:42:05 -0700	[thread overview]
Message-ID: <20160921164205.000645d8@xeon-e3> (raw)
In-Reply-To: <20160921172905.GA7158@mhcomputing.net>

On Wed, 21 Sep 2016 10:29:05 -0700
Matthew Hall <mhall@mhcomputing.net> wrote:

> 5. It uses "malloc" instead of standard DPDK allocators. That's bad for me 
> because I don't want to use libc malloc in my code. Only DPDK allocators and 
> jemalloc.

This was intentional because rte_malloc comes out of huge page area and that
resource is a critical resource. It could use rte_malloc() but that makes it
more likely to break when doing Policy Based routing or VRF.

The BSD tree was used because it was space/time efficient lookup and available
on both BSD and Linux.

  parent reply	other threads:[~2016-09-21 23:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 20:04 Shyam Sundar Govindaraj
2016-09-19 21:18 ` Nikita Kozlov
2016-09-19 21:22   ` Matthew Hall
2016-09-20 20:11     ` Thomas Monjalon
2016-09-21 17:29       ` Matthew Hall
2016-09-21 19:37         ` Thomas Monjalon
2016-09-21 23:42         ` Stephen Hemminger [this message]
2016-09-22  1:50           ` Matthew Hall
2016-09-22  5:07             ` Stephen Hemminger
2016-09-22 17:55               ` Matthew Hall
2016-09-22 18:09                 ` Stephen Hemminger
2016-09-22 20:32         ` Nikita Kozlov

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=20160921164205.000645d8@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=mhall@mhcomputing.net \
    --cc=nikita@gandi.net \
    --cc=thomas.monjalon@6wind.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).