vcl: fix vcl issue in multi-thread-workers mode

   In some multi-process/thread applications, a connection FD
is created on main process and actual data processing is done
in worker process. The main process does nothing. For such
applications, when multi-thread-workers is enabled, in current
VLS code, the session events are still enqueued to the VCL
worker corresponding to Main process. As the main process is
not dequeuing any event, application doesn't move forward.
This patch fixes this issue by enabling VCL worker
corresponding to the Worker process as listener of the session.

Type: improvement

Signed-off-by: Mohamed Feroz <mabdulmajeet@marvell.com>
Change-Id: Ia7e6270c1acbce7feeafbf281c661285d63c3b22

diff --git a/src/vcl/vcl_locked.c b/src/vcl/vcl_locked.c
index 69dd15b..93ece00 100644 (file)
--- a/src/vcl/vcl_locked.c
+++ b/src/vcl/vcl_locked.c
@@ -374,6 +374,12 @@ vls_worker_get_current (void)
   return pool_elt_at_index (vlsm->workers, vls_get_worker_index ());
 }
 
+static inline u8
+vls_n_workers (void)
+{
+  return pool_elts (vlsm->workers);
+}
+
 static void
 vls_worker_alloc (void)
 {
@@ -1298,7 +1304,7 @@ vls_mp_checks (vcl_locked_session_t * vls, int is_add)
   vcl_session_t *s;
   u32 owner_wrk;
 
-  if (vls_mt_wrk_supported ())
+  if (vls_mt_wrk_supported () && vls_n_workers () <= 1)
     return;
 
   ASSERT (wrk->wrk_index == vls->vcl_wrk_index);