Fix multibuffer polling.

Multibuffer thread code never succeeded in joining the polling thread, because the polling thread didn't check thread-local keep_polling variable. This prevented multithreaded software using QAT engine from exiting. Fix a memory leak by matching ptread_key_create() with pthread_key_delete(). Also remove pthread_setspecific() call from thread destructor. Documentation specifies that the thread key value is set to NULL before destructor is called with the previously associated value. Signed-off-by: Ismo Puustinen <ismo.puustinen@intel.com> Signed-off-by: Yogaraj Alamenda <yogarajx.alamenda@intel.com>

Author: ipuustin

qat_sw_init.c

@@ -414,8 +414,6 @@ void mb_thread_local_destructor(void *tlv_ptr)
  } else {
  DEBUG("tlv NULL\n");
  }
-
- pthread_setspecific(mb_thread_key, NULL);
 }
 
 int multibuff_init(ENGINE *e)
@@ -461,5 +459,7 @@ int multibuff_finish_int(ENGINE *e, int reset_globals)
 
  PRINT_RDTSC_AVERAGES();
 
+ ret = pthread_key_delete(mb_thread_key) == 0;
+
  return ret;
 }

qat_sw_polling.c

@@ -357,7 +357,7 @@ void *multibuff_timer_poll_func(void *thread_ptr)
 
  DEBUG("Polling Timeout %ld tlv %p\n", mb_poll_timeout_time.tv_nsec, tlv);
 
- while (multibuff_keep_polling) {
+ while (tlv->keep_polling && multibuff_keep_polling) {
  while ((sig = sigtimedwait((const sigset_t *)&tlv->set, NULL, &mb_poll_timeout_time)) == -1 &&
  errno == EINTR &&
  eintr_count < QAT_SW_NUM_EVENT_RETRIES) {