From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: LPM6 next hop size
Date: Thu, 22 Sep 2016 11:09:14 -0700
Message-ID: <20160922110914.3f7b1854@xeon-e3>
References: <d28c22febc564e45a4c2f5b4066223bc@Hq1wp-exmb11.corp.brocade.com>
 <c57b485f-ff12-7b7c-9ad8-8e9131647069@gandi.net>
 <20160919212257.GA27713@mhcomputing.net> <3263960.cPWMKkvuZx@xps13>
 <20160921172905.GA7158@mhcomputing.net>
 <20160921164205.000645d8@xeon-e3>
 <20160922015034.GA10277@mhcomputing.net>
 <CAOaVG16YuP9R6CSZqSFR=mgHkOauB0dMvAwr12PABcnt5poW4g@mail.gmail.com>
 <20160922175543.GA19530@mhcomputing.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>, "dev@dpdk.org"
 <dev@dpdk.org>, Nikita Kozlov <nikita@gandi.net>
To: Matthew Hall <mhall@mhcomputing.net>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pf0-f173.google.com (mail-pf0-f173.google.com
 [209.85.192.173]) by dpdk.org (Postfix) with ESMTP id 4171A567A
 for <dev@dpdk.org>; Thu, 22 Sep 2016 20:09:06 +0200 (CEST)
Received: by mail-pf0-f173.google.com with SMTP id 21so33014370pfy.0
 for <dev@dpdk.org>; Thu, 22 Sep 2016 11:09:06 -0700 (PDT)
In-Reply-To: <20160922175543.GA19530@mhcomputing.net>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Thu, 22 Sep 2016 10:55:43 -0700
Matthew Hall <mhall@mhcomputing.net> wrote:

> On Wed, Sep 21, 2016 at 10:07:46PM -0700, Stephen Hemminger wrote:
> > 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.  
> 
> Won't paging out routes result in very poor network performance?

This is the rules not the LPM table itself. The rules are only used when computing
new LPM after add/delete route.