Date: Sat, 06 Oct 2001 01:46:47 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: hackers@freebsd.org Cc: net@freebsd.org Subject: IPSEC sucking up memory Message-ID: <3BBEC4F7.D15FF792@mindspring.com>
next in thread | raw e-mail | index | archive | help
While investigating a problem, I noticed that the IPSEC code is initializing the sp -- even when no one is using IPSEC. Is there a good reason why this is not late-bound, and the IPSEC code is initializing and copying and checking the security policy pointer, even in the absense of actual use of security over socket links? It turns out that this really, really bloats the per socket memory requirements, with the only real result being a lot of extra processing that could be replaced by a pointer is not NULL check. It seems to me that this could be handled in the TCP, UDP, and IP userreq code by only initializing the thing in the case that a policy has been set. Is there some reason why this can't be done? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BBEC4F7.D15FF792>