Re: Enable functionality by default
On 16/04/2019 22:12, Joerg Sonnenberger wrote: > altq has some significant impact on the network layer and I would expect > just enabling it to have a measureable impact on netio. Ok, forget enabling that then. Thanks, Sevan
Re: Enable functionality by default
On Tue, Apr 16, 2019 at 04:55:41PM +0100, Sevan Janiyan wrote: > Not all of our network drivers support altq altq has some significant impact on the network layer and I would expect just enabling it to have a measureable impact on netio. Joerg
Re: Enable functionality by default
Le mar. 16 avr. 2019 à 17:55, Sevan Janiyan a écrit : > altq, veriexec, BUFQ_PRIOCSCAN, CARP > ... > Are there any reasons not enable these features by default on all ports > (with the exception of resource constrained systems such as sun2, sun3, > zaurus) ? I think enabling veriexec used to incurr some overhead for exec or file copy, but I don't recall details. Jaromir
Enable functionality by default
Hello, There are certain features we've had in our kernel configs which have required a custom kernel to be built in order to enable them. altq, veriexec, BUFQ_PRIOCSCAN, CARP veriexec and BUFQ_PRIOCSCAN have been enabled on amd64, evbarm, macppc for some time now, but haven't been enabled across the board. Not all of our network drivers support altq Not sure why CARP was never enabled by default but it works when I tested it last week on HEAD and it's a useful feature to have out of the box. Are there any reasons not enable these features by default on all ports (with the exception of resource constrained systems such as sun2, sun3, zaurus) ? Sevan
