From: Paolo Abeni <pabeni@redhat.com>
To: Kui-Feng Lee <thinker.li@gmail.com>,
dsahern@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, martin.lau@linux.dev,
kernel-team@meta.com, yhs@meta.com
Cc: Kui-Feng Lee <kuifeng@meta.com>
Subject: Re: [PATCH net-next v2 1/2] net/ipv6: Remove expired routes with a separated list of routes.
Date: Thu, 20 Jul 2023 11:18:54 +0200 [thread overview]
Message-ID: <32fa8af544b90be8c70ac52135fcb75aa7504f21.camel@redhat.com> (raw)
In-Reply-To: <20230718180321.294721-2-kuifeng@meta.com>
On Tue, 2023-07-18 at 11:03 -0700, Kui-Feng Lee wrote:
> FIB6 GC walks trees of fib6_tables to remove expired routes. Walking a tree
> can be expensive if the number of routes in a table is big, even if most of
> them are permanent. Checking routes in a separated list of routes having
> expiration will avoid this potential issue.
>
> Signed-off-by: Kui-Feng Lee <kuifeng@meta.com>
There is a mismatch between the sender (Kui-Feng Lee
<thinker.li@gmail.com>) and the SoB tag, please either change the sob
or add a From: header tag to fix such mismatch.
> @@ -2312,6 +2323,40 @@ static int fib6_age(struct fib6_info *rt, void *arg)
> return 0;
> }
>
> +static void fib6_gc_table(struct net *net,
> + struct fib6_table *tb6,
> + void *arg)
Here 'arg' is actually 'struct fib6_gc_args *', you can/should update
the type (and name) accordingly ...
> +{
> + struct fib6_info *rt;
> + struct hlist_node *n;
> + struct nl_info info = {
> + .nl_net = net,
> + .skip_notify = false,
> + };
> +
> + hlist_for_each_entry_safe(rt, n, &tb6->tb6_gc_hlist, gc_link)
> + if (fib6_age(rt, arg) == -1)
> + fib6_del(rt, &info);
> +}
> +
> +static void fib6_gc_all(struct net *net, void *arg)
... same here.
Cheers,
Paolo
next prev parent reply other threads:[~2023-07-20 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 18:03 [PATCH net-next v2 0/2] Remove expired routes with a Kui-Feng Lee
2023-07-18 18:03 ` [PATCH net-next v2 1/2] net/ipv6: Remove expired routes with a separated list of routes Kui-Feng Lee
2023-07-20 9:18 ` Paolo Abeni [this message]
2023-07-20 16:31 ` Kui-Feng Lee
2023-07-18 18:03 ` [PATCH net-next v2 2/2] selftests: fib_tests: Add a test case for IPv6 garbage collection Kui-Feng Lee
2023-07-20 9:32 ` Paolo Abeni
2023-07-20 16:32 ` Kui-Feng Lee
2023-07-20 21:36 ` Kui-Feng Lee
2023-07-21 7:14 ` Paolo Abeni
2023-07-21 18:31 ` Kui-Feng Lee
2023-07-21 20:01 ` David Ahern
2023-07-21 20:57 ` Kui-Feng Lee
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=32fa8af544b90be8c70ac52135fcb75aa7504f21.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=thinker.li@gmail.com \
--cc=yhs@meta.com \
/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;
as well as URLs for NNTP newsgroup(s).