Your message dated Tue, 18 Mar 2008 09:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#444277: fixed in iperf 2.0.2-4
has caused the Debian Bug report #444277,
regarding iperf shows network slowdown with CFS/2.6.23; sched_yield() 
considered harmful;
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
444277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444277
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: iperf
Version: 2.0.2-3
Severity: important

I recenttly reported to the kernel folks that network performance as
measured with iperf goes down significantly from 2.6.22 to 2.6.23 and
I tracked it down to the introduction of CFS (see
<http://lkml.org/lkml/2007/9/26/55>).  During this discussion, Mike
Galbraith noticed that iperf recently added a call to sched_yield()
(see <http://lkml.org/lkml/2007/9/26/82>).  Ingo Molnar concluded that
this was bogus and suggested a proper patch for iperf:
http://lkml.org/lkml/2007/9/26/132
Stephen Hemminger also claimed that a similar patch was submitted by
the BSD people (<http://lkml.org/lkml/2007/9/26/209>,
<http://lkml.org/lkml/2007/9/26/215>).

I suspect quite a few other users will see a slowdown as measured with
iperf when they move to 2.6.23, so it would be good if iperf would
stop using sched_yield() soon.  Maybe you can apply one of the patches
above (I tested Ingo's patch and it worked) or better yet work with
upstream to get this into a new release.

Thanks.
-- 
Martin Michlmayr
http://www.cyrius.com/



--- End Message ---
--- Begin Message ---
Source: iperf
Source-Version: 2.0.2-4

We believe that the bug you reported is fixed in the latest version of
iperf, which is due to be installed in the Debian FTP archive:

iperf_2.0.2-4.diff.gz
  to pool/main/i/iperf/iperf_2.0.2-4.diff.gz
iperf_2.0.2-4.dsc
  to pool/main/i/iperf/iperf_2.0.2-4.dsc
iperf_2.0.2-4_i386.deb
  to pool/main/i/iperf/iperf_2.0.2-4_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roberto Lumbreras <[EMAIL PROTECTED]> (supplier of updated iperf package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 18 Mar 2008 09:12:52 +0100
Source: iperf
Binary: iperf
Architecture: source i386
Version: 2.0.2-4
Distribution: unstable
Urgency: low
Maintainer: Roberto Lumbreras <[EMAIL PROTECTED]>
Changed-By: Roberto Lumbreras <[EMAIL PROTECTED]>
Description: 
 iperf      - Internet Protocol bandwidth measuring tool
Closes: 444277
Changes: 
 iperf (2.0.2-4) unstable; urgency=low
 .
   * Reverted patch to fix bug #431366; added proper patch for performance
     problem with kernels using CFS (>= 2.6.23) (closes: #444277).
   * debian/rules: using simple-patchsys from cdbs.
   * Standards 3.7.3 (no changes).
   * doc-base: changed section to Network/Monitoring section.
Files: 
 cbfb62941ff55ac5a5c4f88012572bbe 586 net optional iperf_2.0.2-4.dsc
 482cf592f32c76ce57ca4efebafdb294 83704 net optional iperf_2.0.2-4.diff.gz
 13f3bb03ea59337f95033253fbcfaf96 47748 net optional iperf_2.0.2-4_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH340YfIEQE/XJcI0RAgThAKDqh7ddNupbAYP/A+I3GZj0MQZmsACfYmtF
qsNvmiUwG5Ciq5EmRY3JDVg=
=Sgxj
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to