feat: store transmit messages in memory pool
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c
- Domain
- embedded-iot
Research direction
Start by tracing the existing block-pool message handling, current transmit message creation, and the transmit queue. Implement and connect rtcan_msg_alloc() across those paths, then verify that transmit messages are allocated from the pool, passed by pointer, and freed after transmission.
Written by the indexing model from the issue text.
Description
Description
Received messages are currently stored in a block pool, whereas transmit messages are copied around (into queue, out of queue, to CAN FIFO). Transmit messages could also be put into the block pool to reduce copying.
Requirements
- Add
rtcan_msg_alloc()function to allocate memory for a message. - Replace existing message creations with
rtcan_msg_alloc(). - Pass pointers to created message through transmit queue.
- Free messages after transmission.
- Dominant language
- C
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from sufst/rtcan
-
feature
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
feature
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
feature
-
good first issue low priority refactor
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
feature priority
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Similar issues
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Shipwright#7229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
riscv-software-src/riscv-isa-sim#2435 · 1 comment ·
-
bug Self Built Image SNAPSHOT Supported Device target/ramips
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100