Date: Tue, 23 Oct 2001 13:04:49 +0900 From: Shoichi Sakane <sakane@kame.net> To: tlambert2@mindspring.com Cc: hackers@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: IPSEC sucking up memory Message-ID: <20011023130449I.sakane@kame.net> In-Reply-To: Your message of "Sat, 06 Oct 2001 01:46:47 -0700" <3BBEC4F7.D15FF792@mindspring.com> References: <3BBEC4F7.D15FF792@mindspring.com>
next in thread | previous 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. > 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? IPsec specification requires to consult the SPD with all of packets in order to handling the packet. it defines RFC2401. if a pointer to the entry of the SPD is NULL, it means the security policy is not defined. so the kernel consults the system wide default. it never means nothing to do. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011023130449I.sakane>