[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a02e8fbb-8579-4cce-9868-73c8bbac4720@gmail.com>
Date: Sun, 14 Jan 2024 14:21:34 +0100
From: Nicolas Maier <nicolas.maier.dev@...il.com>
To: Oliver Hartkopp <socketcan@...tkopp.net>, mkl@...gutronix.de,
linux-can@...r.kernel.org
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, corbet@....net, netdev@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] can: bcm: add recvmsg flags for own, local and remote
traffic
Hello,
Thanks a lot for the feedback!
On 08/01/2024 19:57, Oliver Hartkopp wrote:
> But in the first place I'm interested to know what the use-case for this
> extension is.
My goal with this extension is to be able to implement a reliable
'CAN send' function in userspace which would check that the message has
been correctly transmitted, or retry if no confirmation was received
after a timeout (I am using a device which empties some TX buffer when
recovering from the Bus-Off state, therefore some messages will be lost,
which is why the reliability needs to be handled elsewhere). For this
purpose, knowing the origin of a received message is needed.
This was already possible with RAW sockets, and the goal here is to
provide the same information when using BCM sockets.
Best regards,
Nicolas
Powered by blists - more mailing lists