I've corrected our advisory and sent out a new version. Once again, sorry for giving the wrong impression. I believe this comes from a copy-and-paste of some much earlier text that was written before you started actively maintaining iperf2 (that does not excuse the error, but that's probably why it happened).
Bruce. I wrote: > Hi Bob-- > > Apologies! The text "older version" wasn't right and didn't even contribute > any value in the context where it was used. I'm not sure how that phrase got > included, but that mistake is definitely mine. > > Thanks for the update on iperf2 activities. We've been working on adding > multi-threading capabilities to iperf3, so that it can use multiple CPU cores > for higher throughput testing. (Of course, iperf2 has had this ability for > quite awhile.) We've done a few public betas over the summer, with generally > useful and favorable results. The plan is to bring this into a mainline > release "soon". > > Bruce. > > If memory serves me right, Bob McMahon wrote: > >> Thanks for this Bruce & to the iperf 3 team. >> >> A small correction - not sure I'd say iperf2 is an older version but rather >> another version based from the original iperf code (using those design >> patterns.) The latest version for iperf 2 is version 2.1.9 released on >> March 14, 2023. One can always compile the bleeding edge from source per >> the master branch. Those commits come in spurts but can be daily. Some new >> multicast code was committed yesterday as an example. [snip]
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Iperf-users mailing list Iperf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iperf-users
