The minimum execution unit of the CPU is a thread, and the coprocessor does not require QT support ... Just use the ready-made co-libraries.

The process also has the advantage in I/O operations, the QT event loop, the ability to many I/O is already asynchronous, the use of good asynchronous (although all say async a little anti-human thinking).
Because the CPU executes the smallest unit is the thread, the co-process is only on top of it and dispatched.

I mean to take advantage of good async.
The process is program-level scheduling, and there is no advantage for CPU execution.

The smallest execution unit of the CPU is the thread, the single-line thread 100,000-way, also is one in the work, cannot utilize the parallel superiority.
For high-operation programs, the Co-op has no advantage over increasing the scheduling overhead.
It is useful for programs that have more I/O operations because I/O is too slow. and the corresponding I/O operation, the asynchronous relative and the co-process overhead is smaller, more efficient.
CPP also has libraries, some are based on ASIO implementation, many of the bottom is also the event loop.
And QT itself is the event loop, most I/O is also asynchronous, why not first consider the use of good asynchronous and event loop to optimize.

QT support is not required for co-process ... Just use the ready-made co-libraries.

Http://www.qtcn.org/bbs/read-htm-tid-60287.html

The minimum execution unit of the CPU is a thread, and the coprocessor does not require QT support ... Just use the ready-made co-libraries.