net/tcp: Use highest priority for TCP internal work queue
Reason why the prority was at its lowest is unknown, but now that it may
be used to send local packets (which used to be sent right away),
it seems to affect TCP scheduling in loopback mode. Raising the prority
so it matches how it was previously (i.e. sent right away) should fix
things. (Note however that this issue was not broadly present, only
sockets.tls test seemed to be affected.)
Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
diff --git a/subsys/net/ip/tcp2.c b/subsys/net/ip/tcp2.c
index ca16d01..99376ba 100644
--- a/subsys/net/ip/tcp2.c
+++ b/subsys/net/ip/tcp2.c
@@ -2823,10 +2823,9 @@
#endif
#if IS_ENABLED(CONFIG_NET_TC_THREAD_COOPERATIVE)
-/* Lowest priority cooperative thread */
-#define THREAD_PRIORITY K_PRIO_COOP(CONFIG_NUM_COOP_PRIORITIES - 1)
+#define THREAD_PRIORITY K_PRIO_COOP(0)
#else
-#define THREAD_PRIORITY K_PRIO_PREEMPT(CONFIG_NUM_PREEMPT_PRIORITIES - 1)
+#define THREAD_PRIORITY K_PRIO_PREEMPT(0)
#endif
/* Use private workqueue in order not to block the system work queue.
