Features/network reentrant: Difference between revisions
(Created page with 'The network layer re-entrant includes: network core backend, like tap frontend network core The thread-safety of NetClientState and NetQueue. (proposal patches have be…') |
No edit summary |
||
| Line 1: | Line 1: | ||
The network layer re-entrant includes: | The network layer re-entrant includes the following efforts: | ||
network core | re-entrant for network core | ||
backend | re-entrant for backend like tap | ||
frontend | re-entrant for frontend like virtio net | ||
network core | network core | ||
The thread-safety of NetClientState and | The thread-safety of NetClientState, NetQueue and hub. (proposal patches have been sent out) | ||
backend | backend | ||
using glib as the event loop | using glib as the event loop to make them thread safe | ||
frontend | frontend | ||
Depend on other Qemu subsystem's re-entrant. Currently, the main blockers are memory, interrupt. | Depend on other Qemu subsystem's re-entrant. Currently, the main blockers are memory, interrupt. | ||
Revision as of 02:52, 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)
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.