Project

General

Profile

Bug #6553

net.inet.ip.dummynet.pipe_slot_limit can't be set manually, should be automatic

Added by Chris Buechler over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Category:
Limiters
Target version:
Start date:
06/28/2016
Due date:
% Done:

0%

Estimated time:
Affected Version:
All
Affected Architecture:

Description

net.inet.ip.dummynet.pipe_slot_limit only exists after dummynet is kldloaded, which comes after the sysctls are applied. That order's the same in rc.bootup as it's always been, and that did apply cleanly from tunables in past versions, but something's changed where dummynet isn't loaded where it was before.

Regardless it shouldn't be necessary to manually set that, we can set it automatically to the appropriate maximum value.

Associated revisions

Revision ef7c3a63 (diff)
Added by Chris Buechler over 3 years ago

Set pipe_slot_limit to the maximum configured qlimit value. Move the set_sysctl out if the block where it only gets run if dummynet isn't already loaded. Ticket #6553

Revision fcd9f64c (diff)
Added by Chris Buechler over 3 years ago

Set pipe_slot_limit to the maximum configured qlimit value. Move the set_sysctl out if the block where it only gets run if dummynet isn't already loaded. Ticket #6553

Revision ba2c8ed4 (diff)
Added by Chris Buechler over 3 years ago

Set pipe_slot_limit to the maximum configured qlimit value. Move the set_sysctl out if the block where it only gets run if dummynet isn't already loaded. Ticket #6553

History

#1 Updated by Chris Buechler over 3 years ago

  • Status changed from Confirmed to Feedback

fix pushed

#2 Updated by Chris Buechler over 3 years ago

  • Status changed from Feedback to Resolved

works

#3 Updated by Chris Buechler over 3 years ago

  • Target version changed from 2.3.1-p6 to 2.3.2

Also available in: Atom PDF