RT-Thread / RT-Thread/rt-thread
AT的URC处理效率问题
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 12.2k
- Forks
- 5.4k
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 40
Description
这里底层设备IO单次只读1字节，且每个字节都会进行URC表查找，这样的效率是不是太慢，如何RT
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading components/net/at/src/at_client.c around line 688. Confirm how the device I/O read size and URC table lookup are handled for each byte, then determine the intended efficiency change and how it should be measured; the issue does not define acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100