From: Jan Kiszka <jan.kiszka@domain.hid>
To: "gilles.chanteperdrix" <gilles.chanteperdrix@xenomai.org>
Cc: adeos-main <adeos-main@gna.org>
Subject: Re: [Adeos-main] [PATCH+HACK] optimise root stalling
Date: Tue, 26 Sep 2006 17:14:10 +0200 [thread overview]
Message-ID: <451943C2.4070104@domain.hid> (raw)
In-Reply-To: <J67GO9$2B9117C0B95CB2D9676C399264D0207F@laposte.net>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
gilles.chanteperdrix wrote:
> ---------- Debut du message initial -----------
>
> De : adeos-main-bounces@domain.hid
> A : adeos-main@gna.org
> Copies :
> Date : Mon, 25 Sep 2006 12:44:02 +0200
> Objet : Re: [Adeos-main] [PATCH+HACK] optimise root stalling
>
>> Jan Kiszka wrote:
>>> ...
>>> A further idea of mine was to inline light-weight parts of the
>>> __ipipe_*_root API on UP (no SMP at hand to judge on it as
> well).
>> BTW: I haven't looked at any detail yet, but would PER_CPU
> here and
>> there (e.g. for ipipe_percpu_domain) buy us something on SMP
> (2.6)?
>
> I think to remember that the PER_CPU support uses
> smp_processor_id(),
> and we know that smp_processor_id() must not be used over Xenomai
> stacks.
>
Not necessarily: per_cpu(var, cpu) retrieves a variable for the given
cpu without touching smp_processor_id.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-09-26 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 15:07 [Adeos-main] [PATCH+HACK] optimise root stalling gilles.chanteperdrix
2006-09-26 15:14 ` Jan Kiszka [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-25 7:35 Jan Kiszka
2006-09-25 10:44 ` Jan Kiszka
2006-09-28 15:33 ` Philippe Gerum
2006-09-28 9:07 ` Philippe Gerum
2006-09-28 9:15 ` Jan Kiszka
2006-09-28 9:16 ` Philippe Gerum
2006-09-28 9:23 ` Jan Kiszka
2006-09-28 10:07 ` Philippe Gerum
2006-09-28 10:31 ` Jan Kiszka
2006-09-28 10:46 ` Philippe Gerum
2006-09-29 7:48 ` Jan Kiszka
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=451943C2.4070104@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=adeos-main@gna.org \
--cc=gilles.chanteperdrix@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.