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

thread_policy_set not supported for M series chips #5524

Open
1 task done
Lovely-XPP opened this issue Dec 21, 2024 · 1 comment
Open
1 task done

thread_policy_set not supported for M series chips #5524

Lovely-XPP opened this issue Dec 21, 2024 · 1 comment
Labels
need more info Issue that requires more info from contributor

Comments

@Lovely-XPP
Copy link

Is there an already existing issue for this?

  • I have searched the existing issues

Expected behavior

Example can nomally run.

Current behavior

After running the example, no response.

Steps to reproduce

Directly complime and the examples and they can not run.

Fast DDS version/commit

3.1.0

Platform/Architecture

Other. Please specify in Additional context section.

Transport layer

Default configuration, UDPv4 & SHM, TCPv4

Additional context

Platform: MacOS 15.2 Arm 64
截屏2024-12-22 00 01 54

thread_policy_set not supported for M series chips yet, therefore the function return 46 (KERN_NOT_SUPPORTED), then run into EPROSIMA_LOG_ERROR and stuck.

My temporary solution: if (0 != result) -> if (KERN_SUCCESS != result && result != KERN_NOT_SUPPORTED)

Refrences:

XML configuration file

No response

Relevant log output

No response

Network traffic capture

No response

@Lovely-XPP Lovely-XPP added the triage Issue pending classification label Dec 21, 2024
@EugenioCollado
Copy link
Contributor

Hi @Lovely-XPP,

The KERN_NOT_SUPPORTED (46) error from thread_policy_set() is expected since this function isn’t supported on the platform. The log is meant to inform about this limitation, and aside from not setting the thread's affinity, it shouldn’t cause any issues.

Could you clarify where exactly you’re getting stuck? Is it the log itself, or something else? Any additional details would help us better understand the problem and assist you further.

If support for this platform is critical for your use case, feel free to reach out so we can explore possible solutions or adaptations.

@EugenioCollado EugenioCollado added need more info Issue that requires more info from contributor and removed triage Issue pending classification labels Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need more info Issue that requires more info from contributor
Projects
None yet
Development

No branches or pull requests

2 participants