[dpdk-dev] LPM6 next hop size

Stephen Hemminger stephen at networkplumber.org
Thu Sep 22 07:07:46 CEST 2016


If you have 2G of huge memory and one 16M routes then the rules start to
kill an application.
Since huge memory is unpageable (pinned) then it is limited.

On Wed, Sep 21, 2016 at 6:50 PM, Matthew Hall <mhall at mhcomputing.net> wrote:

> On Wed, Sep 21, 2016 at 04:42:05PM -0700, Stephen Hemminger wrote:
> > 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.
>
> Can we get more clarity on why PBR or VRF would break it? The performance
> and
> fragmentation of the default glibc allocator are quite bad. So I am trying
> to
> avoid it in my app for example.
>
> Matthew.
>


More information about the dev mailing list