mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas Maier <nicolas.maier.dev@gmail.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
	mkl@pengutronix.de, linux-can@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, corbet@lwn.net, netdev@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] can: bcm: add recvmsg flags for own, local and remote traffic
Date: Sun, 14 Jan 2024 14:21:34 +0100	[thread overview]
Message-ID: <a02e8fbb-8579-4cce-9868-73c8bbac4720@gmail.com> (raw)
In-Reply-To: <14e86ea6-e038-4702-957a-39af27bfc280@hartkopp.net>

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


      reply	other threads:[~2024-01-14 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-07  6:44 Nicolas Maier
2024-01-08 18:57 ` Oliver Hartkopp
2024-01-14 13:21   ` Nicolas Maier [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a02e8fbb-8579-4cce-9868-73c8bbac4720@gmail.com \
    --to=nicolas.maier.dev@gmail.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=socketcan@hartkopp.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®