[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM0EoM=yX4yWrSrxU4PxVje9E-Qh1GcXkwWRqLybNmQhLXEaHg@mail.gmail.com>
Date: Sat, 9 Nov 2024 08:07:42 -0500
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Alexandre Ferrieux <alexandre.ferrieux@...il.com>
Cc: edumazet@...gle.com, xiyou.wangcong@...il.com, jiri@...nulli.us,
netdev@...r.kernel.org
Subject: Re: [PATCH net v3] net: sched: cls_u32: Fix u32's systematic failure
to free IDR entries for hnodes.
On Thu, Nov 7, 2024 at 6:14 PM Alexandre Ferrieux
<alexandre.ferrieux@...il.com> wrote:
>
> On 07/11/2024 23:58, Alexandre Ferrieux wrote:
> > On 07/11/2024 15:47, Jamal Hadi Salim wrote:
> >> On Thu, Nov 7, 2024 at 9:45 AM Jamal Hadi Salim <jhs@...atatu.com> wrote:
> >>>
> >>> Hi,
> >>>
> >>> On Wed, Nov 6, 2024 at 9:32 AM Alexandre Ferrieux
> >>> <alexandre.ferrieux@...il.com> wrote:
> >>> >
> >>> > Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> >>> > Signed-off-by: Alexandre Ferrieux <alexandre.ferrieux@...nge.com>
> >>>
> >>> I'd like to take a closer look at this - just tied up with something
> >>> at the moment. Give me a day or so.
> >>> Did you run tdc tests after your patch?
> >>
> >> Also, for hero status points, consider submitting a tdc test case.
> >
> > Hi Jamal, thanks for looking into this.
> > Just posted a v4 with a tdc test case.
> > Of course, I also verified that "tdc -c u32" has no regression :)
>
> And a v5 with a proper title as requested by Eric, along with his Reviewed-by.
> (Sorry for violating the rule "one version per 24h" but there's no code change)
>
BTW, what is your interest in u32? I am always curious about use
cases. I gave a talk here:
https://netdevconf.info/0x13/session.html?talk-tc-u-classifier
cheers,
jamal
Powered by blists - more mailing lists