linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Lars Segerlund <lars.segerlund@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: x86 question ...
Date: Tue, 11 Sep 2012 13:42:44 +0200	[thread overview]
Message-ID: <504F23B4.3070003@xenomai.org> (raw)
In-Reply-To: <CAF-VNaqQC94rTrT9E=Dkp0f-NC0YyWXi2rWjsn3XOFMp+feJ9w@mail.gmail.com>

On 09/11/2012 12:55 AM, Lars Segerlund wrote:

>  I read that on arm there was a set of patches for using a single
> virtual adress space, ( ie. all processes live in the same mapping so
> to speak , but still protected ), which greatly reduced context
> switching time on that platform, does anyone know if the same would be
> true for x86 ( maily x86_64 ).


If the patch you are talking about is the FCSE patch, no, it will not
work for x86:
- the FCSE patch allows avoiding to flush the cache at every context
switch on armv4 and armv5, because their cache architecture (VIVT)
requires this cache flush otherwise, but x86 have a PIPT cache, so, no
cache flush is needed during the context switches;
- the FCSE patch requires hardware support, the FCSE (Fast Context
Switch Extension) pid register, despite the fact that every process
lives in a separate 32MiB slice below the 3GB limit, its address-space
appears to be [0;32MiB[, this allows "fork" to work; x86, as far as I
know, has no such hardware.

The advantage compared to uCLinux is that you still have memory
protection, but the performances are probably a bit worse because the
TLB is still invalidated at every context switch. So, these are
different trade-off.

-- 
                                                                Gilles.

      reply	other threads:[~2012-09-11 12:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 22:55 x86 question Lars Segerlund
2012-09-11 11:42 ` Gilles Chanteperdrix [this message]

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=504F23B4.3070003@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=lars.segerlund@gmail.com \
    --cc=linux-rt-users@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).