@@ -2,21 +2,29 @@ Notes for Homa implementation in Linux:
2
2
---------------------------------------
3
3
4
4
* Performance-related tasks:
5
+ * Analyze 40-us W4 short message latency by writing a time-trace
6
+ analyzer that tracks NIC queue length.
5
7
* Perhaps limit the number of polling threads per socket, to solve
6
8
the problems with having lots of receiver threads?
7
9
* Move some reaping to the pacer? It has time to spare
8
10
* Figure out why TCP W2 P99 gets worse with higher --client-max
9
11
* See if turning off c-states allows shorter polling intervals?
10
- * Are Meltdown mitigations really disabled?
11
12
* Consider a permanent reduction in rtt_bytes.
12
13
* Consider reducing throttle_min_bytes to see if it helps region 1
13
14
in the CDF?
14
15
* Modify cp_node's TCP to use multiple connections per client-server pair
15
16
* Why is TCP beating Homa on cp_server_ports? Perhaps TCP servers are getting
16
17
>1 request per kernel call?
17
- * Try measuring performance without polling in Homa?
18
18
19
19
* Things to do:
20
+ * Eliminate hot spots involving NAPI:
21
+ * Arrange for incoming bursts to be divided into batches where
22
+ alternate batches do their NAPI on 2 different cores.
23
+ * To do this, use TCP for Homa!
24
+ * Send Homa packets using TCP, and use different ports to force
25
+ different NAPI cores
26
+ * Interpose on the TCP packet reception hooks, and redirect
27
+ real TCP packets back to TCP.
20
28
* Implement at-most-once semantics:
21
29
* Don't delete server RPCs until acked by client.
22
30
* On client, keep small set of completed RPCs in homa_peer
0 commit comments