From: Andrew Morton <akpm@linux-foundation.org>
To: Eric Dumazet <edumazet@google.com>
Cc: Yixin Shen <bobankhshen@gmail.com>,
leon@kernel.org, davem@davemloft.net,
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 14:20:29 -0700 [thread overview]
Message-ID: <20230414142029.6da5c1bfbf1da82cd0f1c085@linux-foundation.org> (raw)
In-Reply-To: <CANn89i+k9Qn_8bpJb+Cgh_b4VYYVNArSGG3LmR+d3sxjxdxxbw@mail.gmail.com>
On Fri, 14 Apr 2023 16:17:40 +0200 Eric Dumazet <edumazet@google.com> wrote:
> On Fri, Apr 14, 2023 at 4:27 AM Yixin Shen <bobankhshen@gmail.com> wrote:
> >
> > > 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.
>
> This is needed by net/ipv4/tcp_bbr.c , which can be a module.
>
> > If this patch is rejected because the changes are too significant,
>
> Well, this path would soon be reverted by people using bots/tools to
> detect unused functions,
> or unused EXPORT symbols.
>
> So there is no point accepting it, before you submit the CC in the
> official linux tree.
It seems pretty darn screwy that we export minmax_running_max() but not
minmax_running_min().
I'd be OK taking the patch just so we aren't pretty darn screwy. But
it would be perfectly OK to include that one-liner within the patchset
which adds a minmax_running_min() user.
next prev parent reply other threads:[~2023-04-14 21:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 16:47 Yixin Shen
2023-04-13 17:19 ` Leon Romanovsky
2023-04-14 2:27 ` Yixin Shen
2023-04-14 9:00 ` Leon Romanovsky
2023-04-14 14:17 ` Eric Dumazet
2023-04-14 21:20 ` Andrew Morton [this message]
2023-04-14 15:07 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230414142029.6da5c1bfbf1da82cd0f1c085@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bobankhshen@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®