From 9a1a10918615d2138d93a315a6af83253e9d88dd Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Thu, 6 Feb 2014 17:06:00 -0800 Subject: [PATCH] ovs-thread: Add a comment. Reported-by: YAMAMOTO Takashi Signed-off-by: Ben Pfaff --- lib/ovs-thread.h | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/lib/ovs-thread.h b/lib/ovs-thread.h index 8cf2ecca3..f0318948b 100644 --- a/lib/ovs-thread.h +++ b/lib/ovs-thread.h @@ -444,9 +444,15 @@ void xpthread_join(pthread_t, void **); * (by recompiling). Thus, one may more freely use this form of * thread-specific data. * - * Compared to pthread_key_t, ovsthread_key_t has the follow limitations: + * ovsthread_key_t also differs from pthread_key_t in the following ways: * * - Destructors must not access thread-specific data (via ovsthread_key). + * + * - The pthread_key_t API allows concurrently exiting threads to start + * executing the destructor after pthread_key_delete() returns. The + * ovsthread_key_t API guarantees that, when ovsthread_key_delete() + * returns, all destructors have returned and no new ones will start + * execution. */ typedef struct ovsthread_key *ovsthread_key_t; -- 2.43.0