Re: [PATCH v5] kni: allow configuring the kni thread granularity

2022-01-17 Thread Tudor Cornea
On Fri, 14 Jan 2022 at 18:44, Ferruh Yigit wrote: > On 1/14/2022 4:24 PM, Stephen Hemminger wrote: > > On Fri, 14 Jan 2022 17:18:19 +0200 > > Tudor Cornea wrote: > > > >> +module_param(min_scheduling_interval, long, 0644); > >> +MODULE_PARM_DESC(min_scheduling_interval, > >> +"\t\tKni thread min

Re: [PATCH v5] kni: allow configuring the kni thread granularity

2022-01-14 Thread Ferruh Yigit
On 1/14/2022 4:24 PM, Stephen Hemminger wrote: On Fri, 14 Jan 2022 17:18:19 +0200 Tudor Cornea wrote: +module_param(min_scheduling_interval, long, 0644); +MODULE_PARM_DESC(min_scheduling_interval, +"\t\tKni thread min scheduling interval (default=100 microseconds):\n" +"\t\t" +); + +module_par

Re: [PATCH v5] kni: allow configuring the kni thread granularity

2022-01-14 Thread Stephen Hemminger
On Fri, 14 Jan 2022 17:18:19 +0200 Tudor Cornea wrote: > +module_param(min_scheduling_interval, long, 0644); > +MODULE_PARM_DESC(min_scheduling_interval, > +"\t\tKni thread min scheduling interval (default=100 microseconds):\n" > +"\t\t" > +); > + > +module_param(max_scheduling_interval, long, 06

[PATCH v5] kni: allow configuring the kni thread granularity

2022-01-14 Thread Tudor Cornea
The Kni kthreads seem to be re-scheduled at a granularity of roughly 1 millisecond right now, which seems to be insufficient for performing tests involving a lot of control plane traffic. Even if KNI_KTHREAD_RESCHEDULE_INTERVAL is set to 5 microseconds, it seems that the existing code cannot resch