linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Flodin <erik@flodin.me>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH v2 1/2] can: add support for filtering own messages only
Date: Sun, 16 May 2021 22:02:46 +0200	[thread overview]
Message-ID: <CAAMKmocfkcFhhg+JgosbOVZD7AexWEwF6rJzN=Vv86WPFhQYyA@mail.gmail.com> (raw)
In-Reply-To: <64e37aae-e6b5-20aa-04fb-10b4a2f50b5e@hartkopp.net>

Hi again,

Sorry for being slow to reply...

On Mon, 10 May 2021 at 14:28, Oliver Hartkopp <socketcan@hartkopp.net> wrote:
>
>
>
> On 09.05.21 13:28, Erik Flodin wrote:
> > On Thu, 6 May 2021 at 07:26, Oliver Hartkopp <socketcan@hartkopp.net> wrote:
>
> >>>>    From what I understood your main requirement is to double check the
> >>>> outgoing traffic whether is has been sent.
> >>>
> >>> What I would like to have is:
> >>> 1. Be notified when a frame has been sent. I send (from user space) a
> >>> single frame and wait until I get confirmation before sending the next
> >>> to give other nodes on the bus a slot to start sending, even if their
> >>> frames have ID with lower priority.
> >>
> >> o_O
> >>
> >> Sorry, but I have problems to get behind your use-case.
> >>
> >> 1. You are sending a frame
> >> 2. You get a confirmation
> >> 3. You are waiting some time (which is not written above), to give other
> >> nodes a slot??
> >
> > No explicit sleep is needed. The machine is sufficient slow so that
> > just waiting for the confirmation before sending the next frame is
> > enough. But if the frames are queued in the socket/device then the
> > frames are sent back-to-back.
>
> Ok, I feel I'm getting behind your requirement ...
>
> You mainly want to throttle the outgoing traffic, to make sure that e.g.
> a specific CAN ID is not sent 'back-to'back' and might lead to a DoS
> situation on the wire?!?

Yes, so after a frame has been sent, I want to leave the bus idle long
enough to give another device on the bus that has something in its TX
queue an opportunity to send.

> Do you know about the Linux CAN queuing disciplines that might provide
> the solution to your question?

Yes, I came across that when I started my journey in CAN-land, but
unfortunately the kernel I have to use doesn't have support for
traffic control. That's when I started using RECV_OWN_MSGS which
worked until I added filters and here we are now :)

If I get the chance to update the kernel (which would have to happen
before my proposed patch could be used anyway) I should perhaps try to
get tc support instead. That would simplify my application at least.

Thanks for your time!

Best regards,
// Erik

  reply	other threads:[~2021-05-16 20:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 20:35 [PATCH v2 0/2] can: Add CAN_RAW_RECV_OWN_MSGS_ALL socket option Erik Flodin
2021-05-04 20:35 ` [PATCH v2 1/2] can: add support for filtering own messages only Erik Flodin
2021-05-05  6:58   ` Oliver Hartkopp
2021-05-05  8:37     ` Erik Flodin
2021-05-05  9:15       ` Oliver Hartkopp
2021-05-05 18:54         ` Erik Flodin
2021-05-06  5:26           ` Oliver Hartkopp
2021-05-09 11:28             ` Erik Flodin
2021-05-10 12:28               ` Oliver Hartkopp
2021-05-16 20:02                 ` Erik Flodin [this message]
2021-05-17  7:36                   ` Oliver Hartkopp
2021-05-17 18:09                     ` Erik Flodin
2021-05-04 20:35 ` [PATCH v2 2/2] can: raw: add CAN_RAW_RECV_OWN_MSGS_ALL socket option Erik Flodin

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='CAAMKmocfkcFhhg+JgosbOVZD7AexWEwF6rJzN=Vv86WPFhQYyA@mail.gmail.com' \
    --to=erik@flodin.me \
    --cc=linux-can@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).