From owner-freebsd-net@freebsd.org Wed Jul 12 09:36:28 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E431D92784 for ; Wed, 12 Jul 2017 09:36:28 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward3h.cmail.yandex.net (forward3h.cmail.yandex.net [87.250.230.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD86C80D26 for ; Wed, 12 Jul 2017 09:36:27 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp1p.mail.yandex.net (smtp1p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b6:6]) by forward3h.cmail.yandex.net (Yandex) with ESMTP id 7971621373; Wed, 12 Jul 2017 12:36:18 +0300 (MSK) Received: from smtp1p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1p.mail.yandex.net (Yandex) with ESMTP id 6A8731780DB7; Wed, 12 Jul 2017 12:36:14 +0300 (MSK) Received: by smtp1p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id ZAyuCR6YJo-aECGTfar; Wed, 12 Jul 2017 12:36:14 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1499852174; bh=lJvjTEb0wwdvPsuizzF69GwTtjEb1a23IfTP9mIv50A=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=JSyHia6jnpEg2GUMvGWzFMXaCBQYzLOM3gpleDXBVeWF0KyGmOshBS4G+htDjSZQm sdeQabGKOtaNeC0ss5Q7oOhYVZDiA2tMDI1DtdHXcTshzclDCsTxI8pu8zht5Hx0vJ qW+cVMzD7XAYrPxDYM3OEg2uHtEvRk4lMzZkKDVs= Authentication-Results: smtp1p.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0 Subject: Re: memory leaks in 11.0? To: Kajetan Staszkiewicz , Konstantin Belousov Cc: freebsd-net@freebsd.org References: <1771938.JUakJLQFm8@energia> <3858976.1e6N5M9emt@energia> <20170712082652.GD1935@kib.kiev.ua> <34090826.WM7W0CICNb@energia> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <37b9e719-0dec-6c9b-c6e2-6c23480bab4e@yandex.ru> Date: Wed, 12 Jul 2017 12:33:31 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <34090826.WM7W0CICNb@energia> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1wXL0OeSdIogp97Tr7x5XaiXHa0mv8vDl" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 09:36:28 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --1wXL0OeSdIogp97Tr7x5XaiXHa0mv8vDl Content-Type: multipart/mixed; boundary="jPV2P869mx9LTUxg21qd7Dw4IQAp7bMER"; protected-headers="v1" From: "Andrey V. Elsukov" To: Kajetan Staszkiewicz , Konstantin Belousov Cc: freebsd-net@freebsd.org Message-ID: <37b9e719-0dec-6c9b-c6e2-6c23480bab4e@yandex.ru> Subject: Re: memory leaks in 11.0? References: <1771938.JUakJLQFm8@energia> <3858976.1e6N5M9emt@energia> <20170712082652.GD1935@kib.kiev.ua> <34090826.WM7W0CICNb@energia> In-Reply-To: <34090826.WM7W0CICNb@energia> --jPV2P869mx9LTUxg21qd7Dw4IQAp7bMER Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 12.07.2017 11:58, Kajetan Staszkiewicz wrote: >>> Thank you for pointing me to that command, now I see that the biggest= >>> allocation is: >>> lltable 3240611 1620278K - 3311016 256,512 >>> >>> I'll push all `vmstat -m` to graphite to see which one is growing. >> >> lltable is the arp table, AFAIU. >=20 > AFAIR you are right. >=20 >> Do you have something unusual configured there, or some non-usual netw= ork=20 > activity ? >=20 > I have non-standard net.link.ether.inet.max_age=3D240. Default value wa= s 1200.=20 > Table size is: >=20 > % arp -an | wc -l > 2410 > % ndp -an | wc -l > 145 >=20 >> I have no idea if some leaks there were known and fixed since 11.0. I think this should be fixed in 11-STABLE and 11.1. There was a reference leak in L2 cache implementation that is fixed in r315956. --=20 WBR, Andrey V. Elsukov --jPV2P869mx9LTUxg21qd7Dw4IQAp7bMER-- --1wXL0OeSdIogp97Tr7x5XaiXHa0mv8vDl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlll7OsACgkQAcXqBBDI oXrFXwf8Dd4eI2aXsEt3NGYHQbK+jdhIWec7HEiZNi0C+Q+cy6KdVX0x5QOcZ+L7 IyFsNeWk/3bvE3D4o9BizWZDo8CxOIrxvC6K1WFH/7k8RQirXhMBBSx3tesb3xP+ aVsr7fNiTMVkP4lXq+/2ah+i6inMtnjmFdn3ClLRLMZWsn0Q8TTOiXwa0eAKpG5L tMCNQSu29Up6SW/Pi0fYo21cYIpzVKtE0lQig8NFdYArQsuqUxolclgf9iQQpdfm sNvEe25LMoxuppryzUigw9a6IyB+ggoD6W4wKmnakpMJpfEksA4ETs/w0NYG7RIV uYd7nvnw3bHHZ81n3bQDM+FJp8qYpw== =QwB6 -----END PGP SIGNATURE----- --1wXL0OeSdIogp97Tr7x5XaiXHa0mv8vDl--