On 02-Mar-18 6:51 PM, Stephen Hemminger wrote:
On Tue, 27 Feb 2018 14:59:29 +0000
Anatoly Burakov <anatoly.bura...@intel.com> wrote:
This API is similar to the blocking API that is already present,
but reply will be received in a separate callback by the caller.
Under the hood, we create a separate thread to deal with replies to
asynchronous requests, that will just wait to be notified by the
main thread, or woken up on a timer (it'll wake itself up every
minute regardless of whether it was called, but if there are no
requests in the queue, nothing will be done and it'll go to sleep
for another minute).
Signed-off-by: Anatoly Burakov <anatoly.bura...@intel.com>
The problem with this callback model is it makes it possible to
have a single wait for multiple events model (like epoll) which
is the most scaleable way to write applications.
I assume there's a typo in there somewhere, because the way it's written
makes it look like an advantage, not a problem :) Some more details on
what exactly is the issue would be welcome though.
--
Thanks,
Anatoly
