Thanks jamie,

In D26782#597232, @csjp wrote:

SOCK_RAW is still used by other subsystems, e.g. configuring firewalls rules among other things. This is the main reason raw sockets were restricted within jails in the first place. I am not seeing how this patch protects other subsystems.

Hi bz,

In D13656#422012, @dchagin wrote:

ok, btw, what is the reason to create only 2 devices (eth0 and lo0)?

updated patch to address style(9) issues.

Fixed latest style issue.

In D13759#397131, @bcr wrote:

Is this still open? I'm not sure manpages needs to approve much here. I'm OK with the change from the doc (comment) side.

Fixed style.

In D13759#288265, @jilles wrote:

It is already possible to disable swapping out kernel stacks via sysctl vm.swap_enabled (which has a wrong description) and configure it via sysctls vm.swap_idle_threshold1 and vm.swap_idle_threshold2. What is the problem you are trying to solve?

Note that a second effect of swapping out is that ps will not attempt to read arguments and environment from the memory of a "swapped out" process. This will make it more likely that the memory containing these will stay paged out.

If your problem is with paging in general, the "laundry" changes to the VM system in FreeBSD 12 may be useful for you. Basically, these changes allow the system to balance better between paging out things (known as "laundering"; usually to swap but could be to files or devices) and discarding cached data (usually from files).

In D13759#288136, @jilles wrote:

For a long time, "swapping out" a process has only made its U area (later, only the kernel stack) pageable. This is a few pages per thread. Therefore, comparing vmspace_resident_count does not seem to make much sense.

Fixed indentation and typo on comment.

updated comment as requested.
indentation fixed

updated manpage to reflect new option system tunable vm.proc_swapout_max

Added whole-process swapping limit