characteristics about the last connection...

$cat /proc/sys/net/ipv4/tcp_no_metrics_save 
0
$


tcp_no_metrics_save

Normally, TCP will remember some characteristics about the last
 connection in the flow cache. If tcp_no_metrics_save is set, then it
 doesn't. Useful for benchmarks or other tests.




net/ipv4/sysctl_net_ipv4.c - 24 identical

   452:   {   
   453:           .procname       = "tcp_no_metrics_save",     
   454:           .data           = &sysctl_tcp_nometrics_save,

github.com/github/linux-2.6.git - GPL - C - More from linux-2.6.git »


dccpmon-1.0.0/get_sys_info.pl - 2 identical

   171: print LOG "/proc/sys/net/ipv4/tcp_no_metrics_save\n";   
  172: $cmd = "/proc/sys/net/ipv4/tcp_no_metrics_save";   
   173: print "cmd=".$cmd."\n";

www.hep.man.ac.uk/u/rich/Tools_Software/dccpmon/dccpmon-1.0.0.tar - Unknown - Perl

test-cases/chunked-size-mem-advise.pl

     8: #  #!/bin/bash     
     9: #  sysctl -w net.ipv4.tcp_no_metrics_save=1;    
    10: #  while true

netsend.berlios.de/test-cases/chunked-size-mem-advise.pl - Unknown - Perl


"A study of large ?ow interactions in high-speed shared networks 
with Grid5000 and GtrcNET-10 instruments".

a selection follows--


As we are using a Linux timer (HZ) of 250 and 1500 bytes’ packet
 size, the max bandwidth would be about 375 MBps, which is large
 enough to use 1 Gbps NICs. The tcp_no_metrics_save variable
 speci?es that the kernel isn’t supposed to remember the TCP
 parameters corresponding to a network route and so ensures the
 independance of each successive experiment.

A study of large ?ow interactions in high-speed
shared networks with Grid5000 and GtrcNET-10
instruments
Romaric Guillier,
Ludovic Hablot,
Yuetsu Kodama,
Tomohiro Kudoh,
Fumihiro Okazaki,
Pascale Primet,
Sébastien Soudan,
Ryousei Takano
November 2006