-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Bluetooth: Mesh: Use relay bufs/pool for brg_cfg #81226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bluetooth: Mesh: Use relay bufs/pool for brg_cfg #81226
Conversation
alxelax
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it really required to have more config options?
What if you add just dependency to the relay buffer\advertiser instances on bridge feature?
Advantages:
It will not require any C code changes. You will not need more KConfig options. There is only one place to configure number of buffers.
Disadvantages:
It requires better documentation with description that you require more buffers if two features are enabled.
My opinion is less entities in both C and KConfig is better than more. It is better maintainable.
|
I previously proposed that the relay advertising set be renamed to a common name, for example: parallel advertising set, which not depends any feature, and can be used by relay, provision and brg_cfg. |
a7dc4d8 to
163eda4
Compare
IMO it's a bit more invasive than the current changes, but not a bad idea. This would require some restructuring and doc changes to functions/Kconfigs such as |
|
This might pose a problem: |
I guess in case of bridging between subnetworks it should be networked xmit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reading this isolated, I am missing half a sentence what these buffer and advertising sets are used for when MESH_RELAY is disabled... not for relaying, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The relay and bridge functionality is quite similar IMO, with relaying you're a middleman for nodes in the same subnet, but with subnet bridge you're a middleman between subnets. So it's kind of relaying. The bt_mesh_net_relay func is used for both: https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/bluetooth/mesh/net.c#L685
f283f41 to
0b64e7a
Compare
Adds support for using relay buffers and advertising set for the subnet bridge feature, even if the relay feature is disabled. Signed-off-by: Håvard Reierstad <[email protected]>
Makes sure that the Network Transmit state is used when using a Subnet Bridge. Signed-off-by: Håvard Reierstad <[email protected]>
0b64e7a to
88da907
Compare
omkar3141
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now it looks aligned. I have tiny thing about name of the KConfig itself (like calling them as "RELAY_BUF_COUNT" as they are more generic now), but let's leave it for now.
Adds support for using relay buffers and advertising set for the subnet bridge feature, even if the relay feature is disabled. Introduces new Kconfig options that allows the user to configure the relay buffer count and advertising sets in the case when the relay feature is disabled.