Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 12 Dec 2021 13:42:08 +0000
From:      Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= <trasz@freebsd.org>
To:        Gleb Smirnoff <glebius@freebsd.org>
Cc:        Kristof Provost <kp@freebsd.org>, src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org
Subject:   Re: git: eb93b99d6986 - main - in_pcb: delay crfree() down into UMA dtor
Message-ID:  <YbX8MNFcj8ijjBrC@v3.localdomain>
In-Reply-To: <YboGFRrOIz1pFN21@FreeBSD.org>
References:  <202112051847.1B5Il2GP030287@gitrepo.freebsd.org> <28AE53F1-2B22-444B-B1EC-1600FA741FE2@FreeBSD.org> <YbmEIsjf7RZBOOAJ@FreeBSD.org> <D85D47CD-1D03-43E7-84A4-579AF48A29E5@FreeBSD.org> <YboGFRrOIz1pFN21@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 1215T0713, Gleb Smirnoff wrote:
> On Wed, Dec 15, 2021 at 10:47:42AM +0100, Kristof Provost wrote:
> K> > My radical opinion is that per-VNET pcb zones should just be eliminated.
> K> > The only thing they serve is imposing maxsockets limit separately for
> K> > each VNET. But we already have the maxsocket limit on the socket zone,
> K> > which is _global_!
> K> >
> K> > Anybody to explain me the sense of the per-VNET per-pcb zone limit
> K> > set to the same maxsockets value? You can't create a pcb without a
> K> > socket, which is guaranteed by the in_pcballoc() prototype. Of course
> K> > I understand that pcbs may outlive the socket. But those pcbs that
> K> > outlive a socket, are eventually garbage collected as their lifetime
> K> > is finite. Anyway jail/VNET was never declared as a resource management
> K> > framework anyway!
> K> >
> K> 
> K> rctl(8) does appear to support per-jail resource limits, but I’m not sure how complete or functional that is.
> 
> The manual doesn't say anything about network resources. The sources
> of in_pcballoc() neither suggest that any per-something resource management
> is done that can prevent allocation.

True.  I'm guessing it should be possible to limit it via 'openfiles'
resource, but there's nothing socket-specific in RCTL.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YbX8MNFcj8ijjBrC>