From: Thierry Bultel <thierry.bultel@basystemes.fr>
To: xenomai@xenomai.org,
Jean-Baptiste Tredez <jean-baptiste.tredez@basystemes.fr>
Subject: [Xenomai] multiple failing writes to XDDP socket seem to block other I/Os
Date: Tue, 17 Nov 2015 11:34:52 +0100 [thread overview]
Message-ID: <564B02CC.6060609@basystemes.fr> (raw)
Hi,
With xenomai-2.6.4 on IMX6, I am facing an issue, that for now, and
unfortunately, I have not been able to
narrow down to a simple test case, but I am still working on it.
Considering the following piece of code, where :
- globalLogFd is a XDDP socket, whose rtp backend is no longer
listening. This works great when the rtp listener pops the messages.
- fp points to a classical text file
--------------
static int cpt;
void foo() { cpt++; };
static int cpt2;
void foo2() { cpt2++; };
--------------
cpt=0;
cpt2=0;
for (uint32_t i = 0; i < index; i++ )
{
fprintf(stdout,"in loop: %d\n", i);
char msg[256];
sprintf(msg, "%d \n",i);
size_t ret = write(globalLogFd,msg,strlen(msg)+1);
if (ret != strlen(msg)+1) {
foo();
}
count++;
fprintf(fp,"%s",m_buffer[i]);
foo2();
}
fflush(fp);
fclose(fp);
The seen effect is that when the XDDP buffer is full, the I/O do not
work anymore after some number of iterations. The cpt and cpt2 counters
have been correctly incremented 'index' times, but neither the fprintf
to stdout, nor the fprintf to fp do anything.
The context is not an RT thread. I am aware that sharing the globalLogFd
between RT and non RT threads is likely not a good idea.
The interesting thing to notice is that subsequent calls to the loop
make the thing happen again -> the fprintf work for a number of times
and then stop (about 300 times on a total of 1000).
Commenting out the write to globalLogFd lets the fprintf work for all
iterations, as expected.
Best regards
Thierry
next reply other threads:[~2015-11-17 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 10:34 Thierry Bultel [this message]
2015-11-18 9:50 ` [Xenomai] multiple failing writes to XDDP socket seem to block other I/Os Philippe Gerum
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=564B02CC.6060609@basystemes.fr \
--to=thierry.bultel@basystemes.fr \
--cc=jean-baptiste.tredez@basystemes.fr \
--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.