From: Wei Wang <wei...@google.com> Date: Wed, 30 Sep 2020 12:21:35 -0700
... > And the reason we prefer 1 kthread per napi, instead of 1 workqueue > entity per host, is that kthread is more configurable than workqueue, > and we could leverage existing tuning tools for threads, like taskset, > chrt, etc to tune scheduling class and cpu set, etc. Another reason is > if we eventually want to provide busy poll feature using kernel threads > for napi poll, kthread seems to be more suitable than workqueue. ... I think we still need to discuss this some more. Jakub has some ideas and I honestly think the whole workqueue approach hasn't been fully considered yet. If this wan't urgent years ago (when it was NACK'd btw), it isn't urgent for 5.10 so I don't know why we are pushing so hard for this patch series to go in as-is right now. Please be patient and let's have a full discussion on this. Thank you.
