From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Narasimhaprasad Yedatore Achutha <Narasimhaprasad_A@infosys.com>
Cc: "Xenomai@xenomai.org" <Xenomai@xenomai.org>
Subject: Re: [Xenomai] CAN Loopback with Recieve own message
Date: Mon, 14 Dec 2015 23:45:18 +0100 [thread overview]
Message-ID: <20151214224518.GF16627@hermes.click-hack.org> (raw)
In-Reply-To: <f032b1abe1d947cab8a89e20759c07a0@CHNSHLMBX32.ad.infosys.com>
On Sat, Dec 12, 2015 at 01:42:01PM +0000, Narasimhaprasad Yedatore Achutha wrote:
> Hello All
>
> I have a question on RT-Socket not supporting Receive own message
> option(CAN_RAW_RECV_OWN_MSGS ) with MSG_CONFIRM flag not
> supported. I'm trying to understand, if we modify the kernel
> driver supporting CAN_RAW_RECV_OWN_MSGS, so that we start
> receiving transmitted message back at the controller, how much an
> impact happens on
>
> - Real time scheduling
>
> - Does CAN message missing cases be frequent at high bus
> - load for real time applications
>
> - Any other impact we need to consider?
>
> Please let me know if anybody has any experience on this or any
> experiments to share?. Any thoughts or advice will be helpful
I do not see any other reason for not having CAN_RAW_RECV_OWN_MSGS
than the fact that nobody needed this, so nobody implemented it.
--
Gilles.
https://click-hack.org
next prev parent reply other threads:[~2015-12-14 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 13:42 [Xenomai] CAN Loopback with Recieve own message Narasimhaprasad Yedatore Achutha
2015-12-14 22:45 ` Gilles Chanteperdrix [this message]
2015-12-15 6:01 ` Narasimhaprasad Yedatore Achutha
2015-12-15 6:23 ` Gilles Chanteperdrix
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=20151214224518.GF16627@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Narasimhaprasad_A@infosys.com \
--cc=Xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.