| 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: <1202457176.31674.12.camel@iris.sw.ru> Date: Fri, 08 Feb 2008 10:52:56 +0300 From: "Denis V. Lunev" <den@...nvz.org> To: righiandr@...rs.sourceforge.net Cc: Linux Netdev List <netdev@...r.kernel.org>, Balbir Singh <balbir@...ux.vnet.ibm.com>, Naveen Gupta <ngupta@...gle.com>, Paul Menage <menage@...gle.com>, Linux Containers <containers@...ts.osdl.org> Subject: RE: cgroup: limit network bandwidth Hello, Andrea! I have occasionally seen your patch on LWN (missed one in netdev@) and have two words about. May be this is not too late. I have missed my entire mailbox yesterday and have not followed the discussion. Pls forgive me. Rate-limiting message receive is nothing good at all. First, if we talk about i386, the most important resource is low memory. There are no more than 1 Gb of it. You suggest to keep it used more time than usual and this usage will not reduce network traffic to the node for UDP cases. For TCP the situation is slightly better. But not quite a big. For a case of rather slow group with a bug traffic you will just eat 64kb * Nsockets of receive buffers. So, resource usage is just increased for a case. This is unfortunate. In order to proper rate-limiting you need to calculate memory used - dropping incoming packets early for UDP - manage TCP window on the base of buffer memory used by the cgroup Regards, Den -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists