From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Ahern Subject: Re: [RFC/RFT, net-next, 00/17] net: Convert neighbor tables to per-namespace Date: Sun, 12 Aug 2018 11:37:06 -0600 Message-ID: <988a697a-984c-8ca8-7846-e62feb4a4aec@gmail.com> References: <20180717120651.15748-1-dsahern@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: nikita.leshchenko@oracle.com, roopa@cumulusnetworks.com, stephen@networkplumber.org, idosch@mellanox.com, jiri@mellanox.com, saeedm@mellanox.com, alex.aring@gmail.com, linux-wpan@vger.kernel.org, netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org To: Vasily Averin , dsahern@kernel.org, netdev@vger.kernel.org Return-path: In-Reply-To: Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 8/12/18 12:46 AM, Vasily Averin wrote: > On 07/17/2018 03:06 PM, dsahern@kernel.org wrote: >> From: David Ahern >> >> Nikita Leshenko reported that neighbor entries in one namespace can >> evict neighbor entries in another. The problem is that the neighbor >> tables have entries across all namespaces without separate accounting >> and with global limits on when to scan for entries to evict. >> >> Resolve by making the neighbor tables for ipv4, ipv6 and decnet per >> namespace and making the accounting and threshold limits per namespace. > > Dear David, > I prepared own patch set to fix this problem and found your one. > It looks perfect for me, and I hope David Miller will merge it soon, > however I have found a few drawbacks: > Hi: I just returned from an extended vacation. I will revive this topic in the next few days. Thanks for the comments. I will address in the next version.