Features/network reentrant: Difference between revisions
No edit summary |
No edit summary |
||
Line 6: | Line 6: | ||
network core | network core | ||
The thread-safety of NetClientState, NetQueue and hub. (proposal patches have been sent out) | The thread-safety of NetClientState, NetQueue and hub. | ||
(proposal patches have been sent out. See:[PATCH v2 0/5] make netlayer re-entrant [http://www.mail-archive.com/qemu-devel@nongnu.org/msg159336.html]) | |||
backend | backend |
Revision as of 03:04, 8 March 2013
The network layer re-entrant includes the following efforts:
re-entrant for network core re-entrant for backend like tap re-entrant for frontend like virtio net
network core
The thread-safety of NetClientState, NetQueue and hub. (proposal patches have been sent out. See:[PATCH v2 0/5] make netlayer re-entrant [1])
backend
using glib as the event loop to make them thread safe
frontend
Depend on other Qemu subsystem's re-entrant. Currently, the main blockers are memory, interrupt.