Permalink
Cannot retrieve contributors at this time
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
2020-Q-A/Alfonso_S._Siciliano_sysctlinfo_a_new_interface_to_visit_the_FreeBSD_sysctl_MIB_and_to_pass_the_objects
Go to fileThis commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
9 lines (7 sloc)
645 Bytes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<bsdimp> [Q]: Why not use nvlist? | |
[A]: It is a good idea to add nvlist to sysctl, so we could manage the opaque values in an "automatic way" in /sbin/sysctl. | |
I wasted time to code sysctlview and nsysctl to manage "manually" every opaque value. | |
<bsdimp> [Q]: Do you have benchmarks on how much faster this is? | |
[A]: I did some test with time(1): https://gitlab.com/alfix/sysctlinfo/-/blob/master/testing/time/time_testing.sh | |
<bsdimp> [Q]: Can the old interface be implemented as a library on top of the new interface? | |
[A]: Yes, it can, it is a good idea; properly the nodes of the old interface should call the function(s) of the new interface. |