Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp4048596ybd; Tue, 25 Jun 2019 13:07:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqyYC76MOJmT1Extm7ZLOk8YGoye+r+UBrNfQ0U/cHiI1kBAbGxCmwQFwmL8d+Y4koqItIV3 X-Received: by 2002:a17:90a:376f:: with SMTP id u102mr704710pjb.5.1561493257088; Tue, 25 Jun 2019 13:07:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561493257; cv=none; d=google.com; s=arc-20160816; b=qtBveP0BcowTZln/oiKbMq8rmZK/JHRsm0BnueO5AvhKriqrRK2o+87aFn3hsWnRgw EkJAoe9meIbeV0vAxFAXgi0SD+KTpTUcIKFpKXaqLA5ktrvXbp540DciDylh+tIGYras s7iM48AGWOrkS3mAGr28W3/TFJHRJNa7dKjN1xgcWz+b274KnGwRavjmXaGYyH3Sjfa3 mhOAmHYXX5YYYyQuyxT3guKlj4okuv2pj+qjd5f99WqQP4AoBwR9YypYk1RERb+WHBIQ Il8Kg1QvZedeN3RtjcXjJo+OZsTeUce8BCw0vJJIjpkkeFTreuX1Zfiw50GzqDB2X/5x D5Zg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=4k0sYJ43Cukvol0AOXa+WHslo5lSzuNJ/XJtG8j69FQ=; b=hNpx23MNVXpLAN+VOrwKdxtWhUeM9JQV0TQ9Yr/r7Gs+U3nyZHEutcLkN94SnR2rF5 Auan2mh1WLeCSpc4RGXIOjJzfQrThwBlCGNSCQ0xQJm8y3eghkQB3j/igCwHvUVOxY0g jMZC19hDaYoeL8/GUefNeioV++7ka+KBOGyfJvb/ODKLCK0XEExciW2XFXg8jZ0rbI4d XK0f/VCEETQlrgQqLZ3bma88QWc1IquTd8dsazwOHCof2TQpB8Ly6CWEqxyqDiJtAMba sAUnmVV0RWOZ87U+7gXhbw+2KasTqbC3XdCFEWm7XFsWRWYoyMTxKTBOU1fFD+VpOVmP TA8Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t19si73753pjr.68.2019.06.25.13.07.12; Tue, 25 Jun 2019 13:07:37 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728214AbfFYUDw (ORCPT + 99 others); Tue, 25 Jun 2019 16:03:52 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:50178 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726691AbfFYUDv (ORCPT ); Tue, 25 Jun 2019 16:03:51 -0400 Received: from localhost (unknown [IPv6:2601:601:9f80:35cd::d71]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 07698126A7C10; Tue, 25 Jun 2019 13:03:50 -0700 (PDT) Date: Tue, 25 Jun 2019 13:03:50 -0700 (PDT) Message-Id: <20190625.130350.859562313660296893.davem@davemloft.net> To: liuhangbin@gmail.com Cc: sukumarg1973@gmail.com, karn@ka9q.net, kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: hard-coded limit on unresolved multicast route cache in ipv4/ipmr.c causes slow, unreliable creation of multicast routes on busy networks From: David Miller In-Reply-To: <20190625061507.GG18865@dhcp-12-139.nay.redhat.com> References: <20181218.215545.1657190540227341803.davem@davemloft.net> <20190625061507.GG18865@dhcp-12-139.nay.redhat.com> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Tue, 25 Jun 2019 13:03:51 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Hangbin Liu Date: Tue, 25 Jun 2019 14:15:07 +0800 > On Tue, Dec 18, 2018 at 09:55:45PM -0800, David Miller wrote: >> From: Sukumar Gopalakrishnan >> Date: Wed, 19 Dec 2018 10:57:02 +0530 >> >> > Hi David, >> > >> > There are two patch for this issue: >> > 1) Your changes which removes cache_resolve_queue_len >> > 2) Hangbin's changes which make cache_resolve_queue_len configurable. >> > >> > Which one will be chosen for this issue ? >> >> I do plan to look into this, sorry for taking so long. >> >> Right now I am overwhelmed preparing for the next merge window and >> synchronizing with other developers for that. >> >> Please be patient. > > Hi David, > > Any progress for this issue? I have absolutely no context from a discussion that happened back in Dec 2018 If it is important to you, please restart the discussion with a new mailing list posting restating the problem from the beginning and reiterating all of the points and arguments that have been made thus far.