zhanghongyu
02e7ed7cc4
net/can: replace net_lock with conn_lock and conn_lock_dev
...
Protect can resources through netdev_lock, conn_lock, and can_list_lock
Signed-off-by: zhanghongyu <zhanghongyu@xiaomi.com>
2025-12-29 09:42:18 +08:00
wangjinjing1
4fa74e4d18
net/can: add write_q free for callback alloc error handling
...
Release the corresponding resources held when the alloc fails
Signed-off-by: wangjinjing1 <wangjinjing1@xiaomi.com>
2025-12-29 09:42:18 +08:00
wangjinjing1
99584588fc
net/can: modify net_unlock location before txnotify for can_sendmsg_buffered.c
...
Release the lock early to reduce the number of thread switches.
Signed-off-by: wangjinjing1 <wangjinjing1@xiaomi.com>
2025-12-29 09:42:18 +08:00
wangjinjing1
3bd4748bc3
net/can: repair callback alloc error handling
...
Release the corresponding resources held when the alloc fails
Signed-off-by: wangjinjing1 <wangjinjing1@xiaomi.com>
2025-12-29 09:42:18 +08:00
zhanghongyu
3e025b5a03
net/can: can protocol uses a separate buffer to cache can data
...
To avoid memory waste, can add support for using an independent iob buffer
The IP protocol often configures CONFIG_IOB_BUFSIZE to be relatively large,
such as 512, for higher throughput. However, the buffer required by CAN is
fixed at a length of 16 or 64. If the system's IOB is directly used,
a lot of memory will be wasted.
Signed-off-by: zhanghongyu <zhanghongyu@xiaomi.com>
2025-12-25 08:56:12 -03:00
wangjinjing1
7b528d903c
net/can: fix compile error
...
variable "conn" not define if CONFIG_NET_SEND_BUFSIZE > 0
Signed-off-by: wangjinjing1 <wangjinjing1@xiaomi.com>
2025-12-25 10:04:42 +08:00
wangjinjing1
8c92be874f
net/can: add write buffer to support nonblock send
...
The sending of can socket can support more scenarios
Signed-off-by: wangjinjing1 <wangjinjing1@xiaomi.com>
2025-12-15 10:19:15 +08:00
