* Sasha Levin <levinsasha928@xxxxxxxxx> wrote: > > > + pthread_create(&thread, NULL, ioeventfd__thread, NULL); > > > +} > > > > Shouldnt this use the thread pool, so that we know about each and > > every worker thread we have started, in one central place? > > Our thread pool currently responds to events - it runs a callback > if it has received a notification to do so. It doesn't manage > threads which have to run all the time like in this case. then it should perhaps be extended to handle that, because it's always good to have explicit enumeration of all worker threads, and because: > > (This might have relevance, see the big-reader-lock mail i sent > > earlier today.) Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html