-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
samples: net: echo_async_select: Use read()/write() if possible #25356
samples: net: echo_async_select: Use read()/write() if possible #25356
Conversation
All checks passed. Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages. |
@cfriedt: Please review too. And I would appreciate if you performed the similar conversion for your socketpair test(s), as was suggested in the original review. (I didn't want to push with that in the original review, given the amount changes you already made, but I would expect you to follow the suggestion given then. Thanks.) |
47a6682
to
17278a8
Compare
I found some really strange behaviour when I used Also, looks like you need to include |
@cfriedt, thanks for looking.
As we discussed, you found that behavior with CONFIG_POSIX_API=n (unless you have a reproduction testcase).
I don't see any such warning with either Zephyr or Linux, and likely reason that CI fails because |
Ah, d'oh, I see the problem - committed extra code lying in my workcopy. Let's call it Friday afternoon. Fixing. |
17278a8
to
0da8a89
Compare
Ok, pushed changes for just echo_async_select, as was intended. |
Ok, I'll create a ticket for socketpair tests. Unfortunately, I have no reviewer privs here, so I can only say 👍 |
Thanks!
Yep, you don't have suitable level of membership so I can add you as a reviewer. However, on any project on github, for any PR, you can go to "Files changed" tab (https://github.com/zephyrproject-rtos/zephyr/pull/25356/files here), then you'll see green "Review changes" button near top left corner. Clicking on it, you can leave you review. (And that would be appreciated, because one of the problem with POSIX subsys is that I'm the only codeowner, so if I submit PR, there can nobody else to review. So, people interested in the POSIX subsys should keep together and help each other with reviews. Thanks.) |
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.
Looks good to me. Regular read(2) write(2) support is a must for streaming APIs.
If build with full POSIX API, use read()/write() instead of recv()/send() calls for sockets. We have read()/write() support for a while, but no samples/tests actually performed at least a build test for it (so it will be done now). Fixes: zephyrproject-rtos#25407 Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
0da8a89
to
19bcc60
Compare
Created a related bug ticket: #25407 , marking for 2.3. |
If build with full POSIX API, use read()/write() instead of
recv()/send() calls for sockets.
We have read()/write() support for a while, but no samples/tests
actually performed at least a build test for it (so it will be
done now).
Fixes: #25407
Signed-off-by: Paul Sokolovsky paul.sokolovsky@linaro.org