Date: Tue, 22 Jan 2008 19:21:49 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-hackers@freebsd.org Subject: Re: gettimeofday() in hping Message-ID: <fn5c7u$i7e$2@ger.gmane.org> In-Reply-To: <479605E2.6070709@moneybookers.com> References: <4795CC13.7080601@moneybookers.com> <868x2i3v8d.fsf@ds4.des.no> <864pd63v2h.fsf@ds4.des.no> <4795FE54.9090606@moneybookers.com> <86lk6i0vzk.fsf@ds4.des.no> <479605E2.6070709@moneybookers.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig903686BDD2D3C21005F85A6F Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Stefan Lambrev wrote: > I do not have HEPT on the servers that I test, but simple test on my=20 > laptop shows > that hping can generate with ACPI-fast ~4MB/s traffic, 5MB/s with HPET > and 8MB/s with TSC.=20 How much can Linux handle? >I didn't check dummy time counter. If you do, it would give a nice indicator of how much the time counters=20 are expensive in both absolute terms and relative to the rest of the=20 stuff the program does (network IO). The "dummy" timecounter just=20 increments a number when called, no time keeping is involved. --------------enig903686BDD2D3C21005F85A6F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHljQ9ldnAQVacBcgRAuvJAKDLDmXtTXM+J3BS8f/Riw87y5d6JgCfR3Ju xRsqIF7H+T8aazZJ3kxOQ64= =wzUH -----END PGP SIGNATURE----- --------------enig903686BDD2D3C21005F85A6F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fn5c7u$i7e$2>