[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL8zT=iZLorBB0Xn3sQZJe7Ky1ptmA_31FVyDHOCuh-rSicZ8A@mail.gmail.com>
Date: Fri, 20 Jan 2012 08:20:08 +0100
From: Jean-Michel Hautbois <jhautbois@...il.com>
To: Rick Jones <rick.jones2@...com>
Cc: netdev@...r.kernel.org
Subject: Re: Interpreting perf stat on netperf and netserver
2012/1/19 Rick Jones <rick.jones2@...com>:
> On 01/19/2012 12:29 AM, Jean-Michel Hautbois wrote:
>>
>> 2012/1/18 Rick Jones<rick.jones2@...com>:
>>>
>>> On 01/18/2012 03:33 AM, Jean-Michel Hautbois wrote:
>>>>
>>>>
>>>> Hi all,
>>>>
>>>> I am currently using netperf/netserver in order to characterize a
>>>> benet emulex network device on a machine with 2 Xeon5670.
>>>> I am using the latest linux kernel from git (3.2.0+).
>>>> I am facing several issues, and I am trying to understand the
>>>> following perf stat launched on netserver :
>>>>
>>>> Performance counter stats for process id '5043':
>>>
>>>
>>>
>>> If you aren't already you may want to gather system-wide data as well -
>>> not
>>> everything networking is guaranteed to run in the netserver's (or
>>> netperf's)
>>> context.
>>>
>>> Might also be good to include the netperf command line driving that
>>> netserver. That will help folks know if the netserver is receiving data
>>> (_STREAM), sending data (_MAERTS) or both (_RR) (though perhaps that can
>>> be
>>> gleaned from the routine names in the profile.
>>
>>
>> Well, I am only launching netserver without any parameter.
>
>
> The netperf command line, not netserver :) The netperf command line will
> tell us what the netserver was asked to and was presumably doing at the time
> the profile was taken.
I launched it using netperf -H 192.168.2.1 -t UDP_STREAM -f m -- -m 4000
The mtu is set to 4096.
JM
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists