Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 08 Mar 2019 15:25:44 -0800 (PST)
Message-Id: <20190308.152544.1392696861540820759.davem@davemloft.net>
To:     brodie.greenfield@alliedtelesis.co.nz
Cc:     stephen@networkplumber.org, kuznet@ms2.inr.ac.ru,
        yoshfuji@linux-ipv6.org, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, chris.packham@alliedtelesis.co.nz,
        luuk.paulussen@alliedtelesis.co.nz
Subject: Re: [PATCH 0/2] Make ipmr queue length configurable
From:   David Miller <davem@davemloft.net>
In-Reply-To: <20190307045729.14972-1-brodie.greenfield@alliedtelesis.co.nz>
References: <20190307045729.14972-1-brodie.greenfield@alliedtelesis.co.nz>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: Brodie Greenfield <brodie.greenfield@alliedtelesis.co.nz>
Date: Thu,  7 Mar 2019 17:57:27 +1300

> We want to have some more space in our queue for processing incoming
> multicast packets, so we can process more of them without dropping
> them prematurely. It is useful to be able to increase this limit on
> higher-spec platforms that can handle more items.
> 
> For the particular use case here at Allied Telesis, we have linux
> running on our switches and routers, with support for the number of
> multicast groups being increased. Basically, this queue length affects
> the time taken to fully learn all of the multicast streams. 
> 
> Changes in v3:
>  - Corrected a v4 to v6 typo.

This is a new feature, and therefore net-next material.  The net-next
tree is closed, please resubmit when it opens back up.