Allow fwp-timing to generate several streams simultaneously

[frescor/fwp.git] / .topmsg

diff --git a/.topmsg b/.topmsg
index 5973efdd1483f5de22102a501b6bdb9d92ac40cf..6611ddaebb7e3fa502f99a5291115e8a0ffa3a06 100644 (file)
--- a/.topmsg
+++ b/.topmsg
@@ -1,17 +1,4 @@
 From: Michal Sojka <sojkam1@fel.cvut.cz>
-Subject: Implemented synchronous and asynchronous sending
-
-The main goal of this big change is to avoid delays caused by CPU
-scheduler when rescheduling from application thread to VRES TX thread.
-According to our fwp-timing.c experiment, these delays can by even
-several milliseconds long.
-
-Now, whenever VRES capacity allows, send operation is invoked directly
-from application thread. Only if the budget is insufficient, the
-message can be queued for sending later by VRES thread, provided that
-asynchronous send was requested. In case of synchronous send, the
-application thread is blocked until the budget is replenished.
-
-Besides the above change, the code was cleaned up a lot.
+Subject: [PATCH] Allow fwp-timing to generate several streams simultaneously
 
 Signed-off-by: Michal Sojka <sojkam1@fel.cvut.cz>