perfsonar-user - Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Brian Candler <>
- To: Aaron Brown <>
- Cc: "" <>
- Subject: Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3
- Date: Wed, 10 Dec 2014 20:59:04 +0000
- Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type; q=dns; s=sasl; b=RYI6A7Q1rC8VziWVE6xvouaHxhEANwG/ x5yxTfSCuASNPIII+88F+Vg3z3sW/C+/oiQPex2+RhrxPao5n0LtkSa7Zbr0g1ze xK7zE4ys8UM+xQzJEMIa3H9ulCE7rMmBtr9PE6y+J8lr74RGgFU0hnTWXIC4O4J4 ++/xxGZ20bk=
Something else weird. bwctl is now saying "40 seconds until test results available" (or 38 or 39 seconds), even though the test itself covers only 10 seconds.
I noticed that after replacing bwctl-* packages with my own compiled/patched ones; but even after putting them back to the yum originals it's still doing it.
I guess I need to trace this code further to understand it :-(
The patch, by the way, is attached. It cleans up some compilation warnings:
- wrong buffer length passed to strncat: strncat copies up to 'n' characters *plus* a trailing zero
- wrong size passed to memcpy/memcmp: sizeof(sid), where sid is function argument uid8_t[16], gives sizeof(uid8_t*) instead
- unsigned<0 can never be true
- missing function prototypes
- (void*)!NULL -> (void*)1L
- assignment of NULL to 'char' member of struct
- extra parentheses around assignment used as truth expression
It may not actually change anything significant: I realised that since memcmp() is only checking the first 8 bytes of sid, it doesn't matter that only 8 bytes of it were copied.
Regards,
Brian.
Attachment:
bwctl-compiler.diff.gz
Description: application/gzip
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, (continued)
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/07/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/07/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Aaron Brown, 12/09/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/09/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/09/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Aaron Brown, 12/10/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/10/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/11/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Aaron Brown, 12/11/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/11/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/07/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/07/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/10/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/11/2014
Archive powered by MHonArc 2.6.16.