Skip to content
  • Hans Petter Selasky's avatar
    Extend the meaning of the CTLFLAG_TUN flag to automatically check if · 3da1cf1e
    Hans Petter Selasky authored
    there is an environment variable which shall initialize the SYSCTL
    during early boot. This works for all SYSCTL types both statically and
    dynamically created ones, except for the SYSCTL NODE type and SYSCTLs
    which belong to VNETs. A new flag, CTLFLAG_NOFETCH, has been added to
    be used in the case a tunable sysctl has a custom initialisation
    function allowing the sysctl to still be marked as a tunable. The
    kernel SYSCTL API is mostly the same, with a few exceptions for some
    special operations like iterating childrens of a static/extern SYSCTL
    node. This operation should probably be made into a factored out
    common macro, hence some device drivers use this. The reason for
    changing the SYSCTL API was the need for a SYSCTL parent OID pointer
    and not only the SYSCTL parent OID list pointer in order to quickly
    generate the sysctl path. The motivation behind this patch is to avoid
    parameter loading cludges inside the OFED driver subsystem. Instead of
    adding special code to the OFED driver subsystem to post-load tunables
    into dynamically created sysctls, we generalize this in the kernel.
    
    Other changes:
    - Corrected a possibly incorrect sysctl name from "hw.cbb.intr_mask"
    to "hw.pcic.intr_mask".
    - Removed redundant TUNABLE statements throughout the kernel.
    - Some minor code rewrites in connection to removing not needed
    TUNABLE statements.
    - Added a missing SYSCTL_DECL().
    - Wrapped two very long lines.
    - Avoid malloc()/free() inside sysctl string handling, in case it is
    called to initialize a sysctl from a tunable, hence malloc()/free() is
    not ready when sysctls from the sysctl dataset are registered.
    - Bumped FreeBSD version to indicate SYSCTL API change.
    
    MFC after:	2 weeks
    Sponsored by:	Mellanox Technologies
    3da1cf1e