| 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
| ||
|
Message-Id: <200611071106.53975.a1426z@gawab.com> Date: Tue, 7 Nov 2006 11:06:53 +0300 From: Al Boldi <a1426z@...ab.com> To: linux-kernel@...r.kernel.org Cc: netdev@...r.kernel.org, linux-net@...r.kernel.org Subject: Re: ZONE_NORMAL memory exhausted by 4000 TCP sockets Zhao Xiaoming wrote: > The latest update: > It seems that Linux kernel memory management mechanisms including > buddy and slab algorisms are not very efficient under my test > conditions that tcp stack requires a lot of (hundreds of MB) packet > buffers and release them very frequently. > Here is the proof. After change my kernel configuration to support > 2/2 VM splition, LOMEM consumption reduced to 270M bytes compared with > 640M bytes of the 1/3 kernel. All test conditions are the same and > memory pages allocated by TCP stack are also the same, 34K ~ 38K > pages. In other words, 'lost' memory changed from ~500M to ~130M. > Thus, I have nothing to do but guessing the much more free pages make > the slab/buddy algorisms more efficient and waste less memory. I kind of agree, and always compile for a 2G/2G VM split, as this also seems to affect certain OOM conditions positively. What isn't quite clear though, why is the 2G/2G VM split not the default? Thanks! -- Al - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists