Date: Sat, 27 Jul 2013 17:28:56 +0200 From: Marko Zec <zec@fer.hr> To: Adrian Chadd <adrian@freebsd.org> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>, freebsd-pf@freebsd.org Subject: Re: De-virtualize V_pf_mtag_z to eliminate kernel panics. Message-ID: <201307271728.56777.zec@fer.hr> In-Reply-To: <CAJ-Vmo=fqZHuWQnO2LQy0MW3VDejZ6UT7Z2ffv6Nz%2BUyxf5MiQ@mail.gmail.com> References: <CAG=rPVdkpj6mPs=nR_%2B3snb14RUA44pDgSMQkZC9vnBP%2BibCGA@mail.gmail.com> <201307271619.51409.zec@fer.hr> <CAJ-Vmo=fqZHuWQnO2LQy0MW3VDejZ6UT7Z2ffv6Nz%2BUyxf5MiQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 27 July 2013 16:48:00 Adrian Chadd wrote: > I'm happy keeping it virtual (it lets us do things like set per-vimage > mbuf tag limits, and having per-vimage mbufs may be a useful long term > stretch goal to have).. we just have to think about this stuff in more > detail. The V_pf_mtag_z zone apparently doesn't have any size limits, so it doesn't enforce mbuf tag limits in pf, and certainly it doesn't enforce any limits outside of PF? And while otherwise I wouldn't terribly object to keep V_pf_mtag_z virtual, if we don't de-virtualize it, would you have an alternative proposal to resolve the panics in PF which Craig wants to have fixed? Finally, while the idea about enforcing per-vnet mbuf (and tag) limits may look neat on the surface, the fact that mbufs may flow freely between vnets makes this idea less trivial to implement than it may appear at the first glance. In any case, IMO that issue is entirely unrelated to the patch Craig proposed, and should be discussed separately. Marko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201307271728.56777.zec>