You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 22, 2019. It is now read-only.
Currently, implementation diversity (e.g. how to get statistics from an interface) is governed by a combination of ifdefs and ad-hoc conditions. This makes it more difficult to support multiple implementations in a single system. For example, if a system uses Wifi chips from different vendors that use vendor-specific extensions rather than standard nl80211/cfg80211, we need a different interface implementation for each interface. However a large part of the different implementations can probably be shared.
Therefore, it is more convenient to use virtual functions, i.e. function pointers in the per-interface struct. This way, specific interface implementations only need to override the functions they care about.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, implementation diversity (e.g. how to get statistics from an interface) is governed by a combination of ifdefs and ad-hoc conditions. This makes it more difficult to support multiple implementations in a single system. For example, if a system uses Wifi chips from different vendors that use vendor-specific extensions rather than standard nl80211/cfg80211, we need a different interface implementation for each interface. However a large part of the different implementations can probably be shared.
Therefore, it is more convenient to use virtual functions, i.e. function pointers in the per-interface struct. This way, specific interface implementations only need to override the functions they care about.
The text was updated successfully, but these errors were encountered: