Le mercredi 06 juillet 2011 à 21:31 -0400, starlight@xxxxxxxxxxx a écrit : > For anyone who may not have read the bugzilla, a > possibly larger concern subsequently discovered is > that actual kernel memory consumption is double the > total of the values reported by 'netstat -nau', at > least when mostly small packets are received and > a RHEL 5 kernel is in use. The tunable enforces based > on the 'netstat' value rather than the actual value > in the RH kernel. Maybe not an issue in the > mainline, but it took a few additional system > hangs in the lab before we figured this out > and divided the 'udm_mem' maximum value in half. > Several problems here 1) Hugepages can be setup after system boot, and udp_mem/tcp_mem not updated accordingly. 2) Using SLUB debug or kmemcheck for instance adds lot of overhead, that we dont take into account (it would probably be expensive to do so). Even ksize(ptr) is not able to really report memory usage of an object. 3) What happens if both tcp and udp sockets are in use on the system, shouls we half both udp_mem and tcp_mem just in case ? Now if you also use SCTP sockets, UDP-Lite sockets, lot of file mappings, huge pages, conntracking, posix timers (currently not limited), threads, ..., what happens ? Should we then set udp_mem to 1% of current limit just in case ? What about fixing the real problem instead ? When you say the system freezes, is it in the UDP stack, or elsewhere ? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>