All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guvenc Gulce <gulceg@domain.hid>
To: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] IDDP send-receive example emits SIGXCPU signal
Date: Wed, 23 Nov 2011 00:31:44 -0800 (PST)	[thread overview]
Message-ID: <1322037104.76183.YahooMailNeo@domain.hid> (raw)
In-Reply-To: <4EBD0A71.7090409@domain.hid>

Yes.. I have enabled the support for iddp sockets in the kernel configuration. It looks like that 

it works with xenomai 2.6.0 when I enable the 

pthread_set_mode_np(0, PTHREAD_WARNSW);
after the socket() and bind() calls. (tested again with the example code from xenomai)

My question is:

Is it designed that way that the calls socket() and bind() for IDDP cause a switch to 

secondary mode and the calls recvfrom() and sendto() do not ? In other words 

does the real-timeliness guarantee exist only for recvfrom() and sendto() ?


Thanks & Regards

Guvenc




----- Original Message -----
From: Gilles Chanteperdrix <gilles.chanteperdrix@domain.hid>
To: Guvenc Gulce <gulceg@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Sent: Friday, November 11, 2011 12:43 PM
Subject: Re: [Xenomai-help] IDDP send-receive example emits SIGXCPU signal

On 11/11/2011 08:04 AM, Guvenc Gulce wrote:
> looks like XENOMAI_SKINCALL3 macro is failing for some reason but I can't 
> 
> explain this behavior as I am using the example code linked with the correct 
> 
> xenomai libraries. Any help would be highly appreciated.

Do you have support for iddp sockets enabled in kernel configuration? If
yes, do you have the same issue with xenomai 2.6.0?

-- 
                                                                Gilles.



  reply	other threads:[~2011-11-23  8:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11  7:04 [Xenomai-help] IDDP send-receive example emits SIGXCPU signal Guvenc Gulce
2011-11-11 11:43 ` Gilles Chanteperdrix
2011-11-23  8:31   ` Guvenc Gulce [this message]
2011-11-23  9:42     ` 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=1322037104.76183.YahooMailNeo@domain.hid \
    --to=gulceg@domain.hid \
    --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.