Skip to content

samples/net/: Experiencing the delayed response from zephyr networking stack #8057

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

Closed
tarunkum opened this issue May 31, 2018 · 3 comments
Closed
Assignees
Labels
area: Networking bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@tarunkum
Copy link
Contributor

tarunkum commented May 31, 2018

I have trying to run sample net demo application on FRDM board. I started with DHCP, HTTP & COAP.

I have found that Release 1.12 the expected response come Which either comes from client or server is delayed. I can eventually say here that the response time is increased.

Under my observation I can say the response time is almost doubled.

For-example :- In case of sample/net/DHCP sample application DHCP Address resolution is taking more time than as compared to previous Release R1.11.

Please look into.

@kumarvikash1 kumarvikash1 added priority: medium Medium impact/importance bug area: Debugging bug The issue is a bug, or the PR is fixing a bug and removed area: Debugging labels May 31, 2018
@nashif
Copy link
Member

nashif commented May 31, 2018

This is to vague and missing lots of information, you need to provide more data

@nashif nashif added the priority: low Low impact/importance bug label May 31, 2018
@nashif nashif removed the priority: medium Medium impact/importance bug label May 31, 2018
@mike-scott
Copy link
Contributor

This could be related to: #8049

With in-progress PR: #8051

@pfalcon pfalcon changed the title samples/net/: Finding the delayed response from zephyr networking stack samples/net/: Experiencing the delayed response from zephyr networking stack Jun 4, 2018
@nashif
Copy link
Member

nashif commented Feb 19, 2019

outdated with no activity and very general, so closing

@nashif nashif closed this as completed Feb 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Networking bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

6 participants