Messages in this thread | | | Date | Tue, 18 Dec 2001 18:52:00 -0200 | From | Arnaldo Carvalho de Melo <> | Subject | Re: [PATCH][RFC 2] cleaning up struct sock |
| |
Em Mon, Dec 17, 2001 at 10:51:34PM -0800, David S. Miller escreveu: > Which brings me to... > > Please let me know if this is something acceptable for 2.5. > > What kind of before/after effect do you see in lat_tcp/lat_connect > (from lmbench) runs?
Improvements on the lat_connect case? :)
2.4.16 TCP latency using 127.0.0.1: 119.3369 microseconds TCP latency using 127.0.0.1: 118.9847 microseconds TCP latency using 127.0.0.1: 118.5139 microseconds TCP latency using 127.0.0.1: 119.1301 microseconds TCP latency using 127.0.0.1: 118.6322 microseconds
TCP/IP connection cost to 127.0.0.1: 429.6667 microseconds TCP/IP connection cost to 127.0.0.1: 430.7692 microseconds TCP/IP connection cost to 127.0.0.1: 431.4615 microseconds TCP/IP connection cost to 127.0.0.1: 430.3846 microseconds TCP/IP connection cost to 127.0.0.1: 435.4615 microseconds
2.4.16-acme5 TCP latency using 127.0.0.1: 119.2639 microseconds TCP latency using 127.0.0.1: 118.6068 microseconds TCP latency using 127.0.0.1: 119.0443 microseconds TCP latency using 127.0.0.1: 119.5683 microseconds TCP latency using 127.0.0.1: 118.9556 microseconds
TCP/IP connection cost to 127.0.0.1: 408.3571 microseconds TCP/IP connection cost to 127.0.0.1: 409.6429 microseconds TCP/IP connection cost to 127.0.0.1: 410.6429 microseconds TCP/IP connection cost to 127.0.0.1: 409.2143 microseconds TCP/IP connection cost to 127.0.0.1: 414.8333 microseconds
More results are coming, this time for local connections on a 8-way box
- Arnaldo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |