From: Philippe Gerum <rpm@xenomai.org>
To: yo sang <stlfatboy@hotmail.com>
Cc: "xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Subject: Re: data modified by second NRT write with same memory location
Date: Tue, 01 Aug 2023 19:29:27 +0200 [thread overview]
Message-ID: <87pm46sm8y.fsf@xenomai.org> (raw)
In-Reply-To: <DM6PR14MB387142813E6733B5C9DEFEE7A30AA@DM6PR14MB3871.namprd14.prod.outlook.com>
yo sang <stlfatboy@hotmail.com> writes:
> Hi,
>
> I was playing with xddp recently, and found a strange situation.
> I modified official example xddp-echo to test my case:
>
> Main()
> * => get socket
> * => bind socket to port 0
> * => open /dev/rtp0
>
> * => create data buf with “first”
> * => write buf to RT domain via write()
> * => modify data buf to “second”
> * => write buf to RT domain via write()
>
> * Start realtime_thread-------------------------------------->----------+
> * => read from NRT domain via recvfrom()
> * => print output: “second"
> * => read from NRT domain via recvfrom()
> * => print output: “second”
>
> If I write twice with same data location, the RT-end will receive “second” twice.
>
> Any comments?
> Thanks
>
>
Please send the shortest possible piece of code illustrating the issue.
--
Philippe.
next prev parent reply other threads:[~2023-08-01 17:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM6PR14MB3871876E6E078D3BE974ADCBA30AA@DM6PR14MB3871.namprd14.prod.outlook.com>
2023-08-01 9:18 ` data modified by second NRT write with same memory location yo sang
2023-08-01 17:29 ` Philippe Gerum [this message]
2023-08-02 1:19 ` yo sang
2023-08-02 6:04 ` yo sang
2023-08-02 7:30 ` Philippe Gerum
2023-08-02 8:14 ` dietmar.schindler
2023-08-02 9:01 ` Philippe Gerum
2023-08-02 8:32 ` yo sang
2023-08-02 8:56 ` Philippe Gerum
2023-08-03 1:03 ` yo sang
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=87pm46sm8y.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=stlfatboy@hotmail.com \
--cc=xenomai@lists.linux.dev \
/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.