|
@@ -19,7 +19,7 @@
|
|
#include "qemu/coroutine.h"
|
|
#include "qemu/coroutine.h"
|
|
#include "9p.h"
|
|
#include "9p.h"
|
|
|
|
|
|
-/**
|
|
|
|
|
|
+/*
|
|
* we want to use bottom half because we want to make sure the below
|
|
* we want to use bottom half because we want to make sure the below
|
|
* sequence of events.
|
|
* sequence of events.
|
|
*
|
|
*
|
|
@@ -29,7 +29,7 @@
|
|
* we cannot swap step 1 and 2, because that would imply worker thread
|
|
* we cannot swap step 1 and 2, because that would imply worker thread
|
|
* can enter coroutine while step1 is still running
|
|
* can enter coroutine while step1 is still running
|
|
*
|
|
*
|
|
- * @b PERFORMANCE @b CONSIDERATIONS: As a rule of thumb, keep in mind
|
|
|
|
|
|
+ * PERFORMANCE CONSIDERATIONS: As a rule of thumb, keep in mind
|
|
* that hopping between threads adds @b latency! So when handling a
|
|
* that hopping between threads adds @b latency! So when handling a
|
|
* 9pfs request, avoid calling v9fs_co_run_in_worker() too often, because
|
|
* 9pfs request, avoid calling v9fs_co_run_in_worker() too often, because
|
|
* this might otherwise sum up to a significant, huge overall latency for
|
|
* this might otherwise sum up to a significant, huge overall latency for
|