Timeline for How does Linux prevent applications from sending more packets than the link can handle without dropping packets?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 8, 2020 at 18:14 | comment | added | Kevin | Here is the line from the help text -P, --parallel # number of parallel client streams to run | |
| Jan 8, 2020 at 16:52 | comment | added | Kevin | Stream as in the 5-tuple flow. A stream/flow is limited to the BW of the interface. The trick is to push multiple streams at the same time, with an aggregate larger then the nic BW | |
| Jan 8, 2020 at 16:07 | comment | added | Useless | What stream? This is UDP, and expecting outbound packet drops seems reasonable. Even if it was TCP, iperf should be nonblocking and we'd expect to hit the EAGAIN/EWOULDBLOCK path rather than simply waiting. | |
| Jan 8, 2020 at 15:45 | review | Late answers | |||
| Jan 8, 2020 at 15:45 | |||||
| Jan 8, 2020 at 15:26 | history | answered | Kevin | CC BY-SA 4.0 |