lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 08 Jun 2007 17:40:16 -0700
From:	Rick Jones <rick.jones2@...com>
To:	hadi@...erus.ca
Cc:	Krishna Kumar2 <krkumar2@...ibm.com>,
	Gagan Arneja <gaagaan@...il.com>,
	Evgeniy Polyakov <johnpol@....mipt.ru>, netdev@...r.kernel.org,
	Sridhar Samudrala <sri@...ibm.com>,
	David Miller <davem@...emloft.net>,
	Robert Olsson <Robert.Olsson@...a.slu.se>
Subject: Re: [WIP][PATCHES] Network xmit batching

jamal wrote:
> On Fri, 2007-08-06 at 10:27 -0700, Rick Jones wrote:
> 
> [..]
> 
> 
>>you cannot take the netperf service demand directly - each netperf is 
>>calculating assuming that it is the only thing running on the system. 
>>It then ass-u-me-s that the CPU util it measured was all for its work. 
>>This means the service demand figure will be quite higher than it really is.
>>
>>So, for aggregate tests using netperf2, one has to calculate service 
>>demand by hand.  Sum the throughput as KB/s, convert the CPU util and 
>>number of CPUs to a microseconds of CPU consumed per second and divide 
>>to get microseconds per KB for the aggregate.
> 
> 
> From what you are saying above seems to me that for more than one proc
> it is safe to just run netperf4 instead of netperf2?

Well, it is easier to be safe on aggregates with netperf4 than netperf2 
although at present it is more difficult to run netperf4 than netperf2


> It also seems reasonable to set up large socket buffers on the receiver.

For bulk transfers I often do.

rick
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ