Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Yixin Shen <bobankhshen@gmail.com>
To:     leon@kernel.org
Cc:     akpm@linux-foundation.org, bobankhshen@gmail.com,
        davem@davemloft.net, edumazet@google.com,
        linux-kernel@vger.kernel.org, ncardwell@google.com,
        netdev@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH net-next] lib/win_minmax: export symbol of minmax_running_min
Date:   Fri, 14 Apr 2023 02:27:36 +0000
Message-Id: <20230414022736.63374-1-bobankhshen@gmail.com>
In-Reply-To: <20230413171918.GX17993@unreal>
References: <20230413171918.GX17993@unreal>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

> Please provide in-tree kernel user for that EXPORT_SYMBOL.

It is hard to provide such an in-tree kernel user. We are trying to
implement newer congestion control algorithms as dynamically loaded modules.
For example, Copa(NSDI'18) which is adopted by Facebook needs to maintain
such windowed min filters. Althought it is true that we can just
copy-and-paste the code inside lib/win_minmax, it it more convenient to
give the same status of minmax_running_min as minmax_running_max.
It is confusing that only minmax_running_max is exported.
If this patch is rejected because the changes are too significant,
I can also understand.

Thanks.