Skip to content
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

Add queues for netlink messages #106

Merged
merged 33 commits into from
Sep 18, 2023
Merged

Add queues for netlink messages #106

merged 33 commits into from
Sep 18, 2023

Conversation

awlx
Copy link
Member

@awlx awlx commented Sep 18, 2023

It adds a separate thread for the netlink processing and a FIFO queue.

This resolves #103

@awlx awlx self-assigned this Sep 18, 2023
@awlx awlx disabled auto-merge September 18, 2023 13:57
@awlx awlx enabled auto-merge September 18, 2023 14:35
@awlx
Copy link
Member Author

awlx commented Sep 18, 2023

Example Debug output:

Sep 18 16:36:38 gw07 wgkex[16630]: 2023-09-18 16:36:38,817,817 DEBUG    [msg_queue.py:39] Queue is not empty current size is 11
Sep 18 16:36:38 gw07 wgkex[16630]: 2023-09-18 16:36:38,817,817 DEBUG    [msg_queue.py:41] Processing queue item dzz4r646646644=' for domain welt
Sep 18 16:36:38 gw07 wgkex[16630]: 2023-09-18 16:36:38,818,818 INFO     [msg_queue.py:47] Processing queue for key dzz4r646646644=' on domain welt with lladdr fe80::2b9:8aff:fea2:c111/128
Sep 18 16:36:38 gw07 wgkex[16630]: 2023-09-18 16:36:38,820,820 DEBUG    [netlink.py:100] Handling links for WireGuardClient(public_key='dzz4r646646644='', domain='welt', remove=False)
Sep 18 16:36:38 gw07 wgkex[16630]: 2023-09-18 16:36:38,924,924 INFO     [netlink.py:104] Updated route for WireGuardClient(public_key='dzz4r646646644=', domain='welt', remove=False)

@awlx awlx merged commit d3885f7 into main Sep 18, 2023
7 checks passed
@awlx awlx deleted the multithread_worker branch September 18, 2023 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move message processing on workers into separate thread
2 participants