Browse Source

It's not just Etherboot that fails to generate TX completions.

tags/v0.9.3
Michael Brown 17 years ago
parent
commit
0958726ebb
1 changed files with 2 additions and 2 deletions
  1. 2
    2
      src/arch/i386/drivers/net/undinet.c

+ 2
- 2
src/arch/i386/drivers/net/undinet.c View File

@@ -335,8 +335,8 @@ static int undinet_transmit ( struct net_device *netdev,
335 335
 
336 336
 	/* Technically, we ought to make sure that the previous
337 337
 	 * transmission has completed before we re-use the buffer.
338
-	 * However, this would break a gPXE-running-over-Etherboot
339
-	 * setup, since Etherboot fails to generate TX completions.
338
+	 * However, many PXE stacks (including at least some Intel PXE
339
+	 * stacks and Etherboot 5.4) fail to generate TX completions.
340 340
 	 * In practice this won't be a problem, since our TX datapath
341 341
 	 * has a very low packet volume and we can get away with
342 342
 	 * assuming that a TX will be complete by the time we want to

Loading…
Cancel
Save