net: sockets: Add socket processing priority
When creating a socket, all of the registered socket implementation are processed in a sequence, allowing to find appropriate socket implementation for specified family/type/protocol. So far however, the order of processing was not clearly defined, leaving ambiguity if multiple implmentations supported the same set of parameters. Fix this, by registering socket priority along with implementation. This makes the processing order of particular socket implementations explicit, giving more flexibility to the user, for example when it's neeed to prioritze one implementation over another if they support the same set of parameters. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
This commit is contained in:
parent
8b851af02a
commit
0dbdcc770d
12 changed files with 58 additions and 25 deletions
|
@ -1203,4 +1203,5 @@ NET_DEVICE_DT_INST_OFFLOAD_DEFINE(0, modem_init, NULL,
|
|||
&api_funcs, MDM_MAX_DATA_LENGTH);
|
||||
|
||||
/* Register NET sockets. */
|
||||
NET_SOCKET_REGISTER(quectel_bg9x, AF_UNSPEC, offload_is_supported, offload_socket);
|
||||
NET_SOCKET_REGISTER(quectel_bg9x, NET_SOCKET_DEFAULT_PRIO, AF_UNSPEC,
|
||||
offload_is_supported, offload_socket);
|
||||
|
|
|
@ -1956,8 +1956,8 @@ static bool offload_is_supported(int family, int type, int proto)
|
|||
return true;
|
||||
}
|
||||
|
||||
NET_SOCKET_REGISTER(ublox_sara_r4, AF_UNSPEC, offload_is_supported,
|
||||
offload_socket);
|
||||
NET_SOCKET_REGISTER(ublox_sara_r4, NET_SOCKET_DEFAULT_PRIO, AF_UNSPEC,
|
||||
offload_is_supported, offload_socket);
|
||||
|
||||
#if defined(CONFIG_DNS_RESOLVER)
|
||||
/* TODO: This is a bare-bones implementation of DNS handling
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue