[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGHK07D1T76yFv8fQ9RVdJ49ieq6Z=6FumgBbf65OyvRnVJp9Q@mail.gmail.com>
Date: Fri, 23 Dec 2022 09:36:54 +1100
From: Jonathan Maxwell <jmaxwell37@...il.com>
To: David Ahern <dsahern@...nel.org>
Cc: Paolo Abeni <pabeni@...hat.com>, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, yoshfuji@...ux-ipv6.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [net-next] ipv6: fix routing cache overflow for raw sockets
On Fri, Dec 23, 2022 at 3:17 AM David Ahern <dsahern@...nel.org> wrote:
>
> On 12/21/22 10:39 PM, Jonathan Maxwell wrote:
> > There are some mistakes in this prototype patch. Let me come up with a
> > better one. I'll submit a new patch in the new year for review. Thanks for
> > the suggestion DavidA.
>
> you are welcome. When you submit the next one, it would be helpful to
> show change in memory consumption and a comparison to IPv4 for a similar
> raw socket program.
Sure will do, I have an ipv4 version of the test program and a better patch.
Initial results are quite similar for resource usage. The ipv6 GC does a good
job at managing memory resources with max_size threshold removed. I'll
include some comparison stats after I test this extensively when I submit
the new patch.
Powered by blists - more mailing lists