Re: route timer pool

On Tue, Apr 19, 2022 at 06:53:28PM +0200, Alexander Bluhm wrote: > On Tue, Apr 19, 2022 at 08:59:25AM +0200, Claudio Jeker wrote: > > On Tue, Apr 19, 2022 at 01:44:40AM +0200, Alexander Bluhm wrote: > > > Hi, > > > > > > Can we use a pool for rttimer_queue_pool? > > > > Another option would be to

Re: route timer pool

On Tue, Apr 19, 2022 at 08:59:25AM +0200, Claudio Jeker wrote: > On Tue, Apr 19, 2022 at 01:44:40AM +0200, Alexander Bluhm wrote: > > Hi, > > > > Can we use a pool for rttimer_queue_pool? > > Another option would be to use static rttimer_queues instead of allocating > them. Not that many timers a

Re: route timer pool

On Tue, Apr 19, 2022 at 01:44:40AM +0200, Alexander Bluhm wrote: > Hi, > > Can we use a pool for rttimer_queue_pool? Another option would be to use static rttimer_queues instead of allocating them. Not that many timers are used. Requires additional changes in the sysctl handlers (but that code is

route timer pool

Hi, Can we use a pool for rttimer_queue_pool? As we run without kernel lock, these pools should have IPL_MPFLOOR protection. ok? bluhm Index: net/route.c === RCS file: /data/mirror/openbsd/cvs/src/sys/net/route.c,v retrieving revi