All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Alex Plits <alex_plits@radwin.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Suggested approach to schedule N-RT work in kernel on a specific CPU core
Date: Sun, 20 Mar 2016 08:25:20 +0100	[thread overview]
Message-ID: <20160320072520.GF3345@hermes.click-hack.org> (raw)
In-Reply-To: <DB5PR06MB1109ECFBDA54A3B1A11457608F8E0@DB5PR06MB1109.eurprd06.prod.outlook.com>

On Sun, Mar 20, 2016 at 07:15:42AM +0000, Alex Plits wrote:
> Hi,
> 
> We have a requirement to schedule N-RT linux kernel specific work  (e.g. workQ) on a dedicated core from an RTDM driver running
> In Xenomai "context".
> The current RTDM API does in fact provide an API to schedule a N-RT workQ but this does not meet our needs as we need the N-RT job to run on
> A dedicated CPU. Current API implementation will run this special workQ on the CPU where the RT scheduling call occurred, so I have 2 queries we need help with -
> 
> 1.       Is there an API/example/configuration that will achieve our needs?
> 
> 2.       In case there isn't what would be the best approach to implement such a mechanism - I can think of solutions but it seems excessive:
> 
> a.       Run another Xenomai thread that has CPU affinity on the target cpu Core which will call a dedicated RTDM blocking call (e.g. IOCTL with semTake) and then the scheduling RTDM driver will release that semaphore - which will re-schedule the thread on the core we need and now it can call a N-RT IOCTL for example.
> 
> b.      Initialize a new WorkQ on I-Pipe init which will be binded on the target cpu Core only then add new RTDM api to schedule work on that WorkQ - although I'm not sure this will work as it will use the VIRQ  mechanism which will somehow need to change cores.

If the Linux kernel provides a function to do this, we could
implement a function mirroring that function in the RTDM API. Looks
simple. Am I missing something ?

-- 
					    Gilles.
https://click-hack.org


  reply	other threads:[~2016-03-20  7:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-20  7:15 [Xenomai] Suggested approach to schedule N-RT work in kernel on a specific CPU core Alex Plits
2016-03-20  7:25 ` Gilles Chanteperdrix [this message]
2016-03-20  7:49   ` Alex Plits
2016-03-20  7:59     ` Gilles Chanteperdrix
2016-03-20  8:20       ` Alex Plits
2016-03-20  8:38         ` Gilles Chanteperdrix
2016-03-20  8:29       ` Alex Plits

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=20160320072520.GF3345@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=alex_plits@radwin.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.