All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Franz Engel <franz_lambert_engel@yahoo.de>
Cc: 'Jan Kiszka' <jan.kiszka@web.de>, xenomai@xenomai.org
Subject: Re: [Xenomai] Context Switch with rtnet
Date: Thu, 20 Sep 2012 19:36:48 +0200	[thread overview]
Message-ID: <505B5430.5050707@xenomai.org> (raw)
In-Reply-To: <003501cd9744$0c80a460$2581ed20$@de>

On 09/20/2012 05:24 PM, Franz Engel wrote:
> Hi Jan,
> 
>>> Hi,
>>>
>>> I've a little problem. I'm using the rtnet.h-header and the following
>> function:
>>> ret = recvfrom ( ethernetConnection.sock, &recBuffer, sizeof (
>>> recBuffer ),0, ( struct sockaddr * )
>>> &ethernetConnection.dest_addr,&destlen );
>>>
>>>
>>> I compiled the program with the xenomai compiling flags and library.
>>>
>>> When I look to the xenomai state I get something like this:
>>> CPU  PID    MSW        CSW        PF    STAT       %CPU  NAME
>>>  22  0      0          834840     0     00000082    0.1  rtnet-stack
>>>  22  0      0          1          0     00000082    0.0  rtnet-rtpc
>>>   0  6262   2          2          0     00300380    0.0
>> qs_robotpositio
>>>   2  6265   2          6          0     00300380    0.0
>> qs_robotpositio
>>>   0  6266   1          1          0     00300380    0.0
>> robotrsiinterfa
>>>   1  6268   1147       2365       0     00300182    0.8
>> robotrsiinterfa
>>>
>>> You can see, I get a lote of context and module switches just as the
>> rtnet-stack itself. Is that normal?
>>
>> Well, I have no clue what you configured, so I can only guess. If your
>> task 6268 is a pure RT task that is not supposed to interact with Linux
>> services, you first of all have a bug in your software stack. You
>> should look for the reason of those mode switches to Linux, e.g. by
>> asking Xenomai to raise SIGXCPU when this happens.
> 
> I use the SIGXCPU signal to look where I get a context switch. It is exactly
> in the line of the recvfrom. I get the same result when I step through my
> code. I debug from line to line and check the /proc/xenomai/state, so I can
> see that the CSW and MSW increases when I step over the recvfrom. I tried my
> code also with the native commands, like rt_recvfrom. But the result is the
> same.

Stepping in gdb causes switches to secondary mode (each step is a switch
to secondary mode).

Anyway, you did not tell us:
- what version of xenomai
- what version of the Linux kernel
- what version of the I-pipe patch
- what architecture
- what NIC

you are using.

-- 
					    Gilles.


  parent reply	other threads:[~2012-09-20 17:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 15:01 [Xenomai] Context Switch with rtnet Franz Engel
2012-09-16 14:29 ` Jan Kiszka
2012-09-20 15:24   ` Franz Engel
2012-09-20 17:33     ` Wolfgang Grandegger
2012-09-20 17:36     ` Gilles Chanteperdrix [this message]
2012-09-21  9:58 ` Kai Bollue
2012-09-21 10:02   ` Gilles Chanteperdrix
2012-09-21 10:08     ` Kai Bollue
     [not found] <mailman.1.1348308001.4459.xenomai@xenomai.org>
2012-09-22 13:20 ` Franz Engel
2012-09-22 13:33   ` Gilles Chanteperdrix
2012-09-22 13:55     ` Franz Engel
2012-09-22 14:02       ` Gilles Chanteperdrix
2012-09-22 13:43   ` 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=505B5430.5050707@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=franz_lambert_engel@yahoo.de \
    --cc=jan.kiszka@web.de \
    --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.