Re: Opteron bandwidth report failure

To: Stephen Hemminger <shemminger --at-- osdl.org>
Subject: Re: Opteron bandwidth report failure
From: Hans Blom <J.Blom --at-- phys.uu.nl>
Date: Fri, 29 Oct 2004 00:42:54 +0200
Cc: iperf-users --at-- dast.nlanr.net
Content-disposition: inline
Content-type: text/plain; charset=us-ascii
In-reply-to: <20041028102710.04f0bf2a --at-- guest-251-240.pdx.osdl.net>
References: <20041028110724.GA255698 --at-- ruunat.phys.uu.nl> <20041028102710.04f0bf2a --at-- guest-251-240.pdx.osdl.net>
Reply-to: iperf-users --at-- dast.nlanr.net
Sender: owner-iperf-users --at-- dast.nlanr.net
User-agent: Mutt/1.4.2.1i

On Thu, Oct 28, 2004 at 10:27:10AM -0700, Stephen Hemminger wrote:
> On Thu, 28 Oct 2004 13:07:24 +0200
> Hans Blom <J.Blom --at-- phys.uu.nl> wrote:
> 
> > Hello All,
> > 
> > At Iperf 2.0 bandwidth reports seem to fail at AMD Opteron, ruunning
> > Debian Linux.
> 
> Did you apply the fix to correctly pickup threads in the configuration.

No, is that the patch send by Mitch Kutzko to this list? That patch was for
Iperf V 1.7.0. Can it also be used for V 2.0? By the way I got the same problem
with Linux 2.4.X at an i686. Also there the pthread library indeed is not
recognised by the V 2.0. configure script both at the AMD64 and the i686. At the
i686 the thread library is found without problems with Iperf V 1.7.0.

    Hans

References:
- Opteron bandwidth report failure
  - From: Hans Blom
- Re: Opteron bandwidth report failure
  - From: Stephen Hemminger

Prev by Date: Re: Opteron bandwidth report failure
Next by Date: DAST: Iperf - aholmes --at-- owlcti.com
Previous by thread: Re: Opteron bandwidth report failure
Next by thread: DAST: Iperf - aholmes --at-- owlcti.com

Other Mailing lists | Author Index | Date Index | Subject Index | Thread Index