summaryrefslogtreecommitdiffstats
path: root/sbin/mount
diff options
context:
space:
mode:
authoradrian <adrian@FreeBSD.org>2011-07-29 23:55:17 +0000
committeradrian <adrian@FreeBSD.org>2011-07-29 23:55:17 +0000
commit9494715d4b3d5d10e2451c54bcb68a5f91c6e5f5 (patch)
treebef087a9b96afa75bc0ba3c855a89fa1b415e925 /sbin/mount
parentdc4300d6056b52d3a073dc873936e564b766e6d0 (diff)
downloadFreeBSD-src-9494715d4b3d5d10e2451c54bcb68a5f91c6e5f5.zip
FreeBSD-src-9494715d4b3d5d10e2451c54bcb68a5f91c6e5f5.tar.gz
Reset the NIC if ANI is enabled or disabled.
Although this may not be what the original sysctl was designed to do, it feels a bit more "expected". Before, if ANI is disabled, the initial ANI parameters are still written to the hardware, even if they're not enabled. "ANI enabled" would then adjust the noise immunity parameters dynamically. Disabling ANI would simply leave the existing noise immunity parameters where they are, and disable the dynamic part. The problem is that disabling ANI doesn't leave the hardware in a consistent, predictable state - so asking a user to disable ANI wouldn't actually reset the NIC to a consistent set of PHY signal detection parameters, resulting in an unpredictable/unreliable outcome. This makes it difficult to get reliable debugging information from the user. Approved by: re (kib)
Diffstat (limited to 'sbin/mount')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud