All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH] userspace: Make CONFIG_SMP default
Date: Fri, 22 Aug 2008 16:56:22 +0200	[thread overview]
Message-ID: <48AED396.3040903@domain.hid> (raw)
In-Reply-To: <48AECCAD.7030405@domain.hid>

Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Gilles Chanteperdrix wrote:
>>> Jan Kiszka wrote:
>>>> Disabling SMP (on platforms where this isn't off by design already) is
>>>> an optimization. In contrast, not enabling it by default is doomed to
>>>> cause problems for users that run ./configure without looking into each
>>>> and every switch - now that CONFIG_SMP is very important for all the
>>>> fast locking stuff.
>>> I would consider setting CONFIG_SMP by default on x86... because on some
>>> other architectures like arm, it is not even yet a valid configuration.
>> But it is on PowerPC or IA64. Would it cause troubles for the
>> non-SMP-ready archs? Then we can disable it on those selectively.
> 
> Are you sure that the lock prefix on an UP x86 or lsync on an UP powerpc
> is hamrless ?

LOCK is harmless (except for potential overhead), can't comment isync,
but I strongly suspect the same (locking at the glibc e.g.). There is a
simple idea behind this: Do you have to install a special glibc in order
to enable/disable SMP support?

[ BTW, I think the current pthread_mutex implementation lacks the LOCK
prefix even in SMP mode due to include issues. Will get fixed with my
patches under preparation, which also unifies that stuff on x86. ]

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


  reply	other threads:[~2008-08-22 14:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22 13:09 [Xenomai-core] [PATCH] userspace: Make CONFIG_SMP default Jan Kiszka
2008-08-22 14:03 ` Gilles Chanteperdrix
2008-08-22 14:10   ` Jan Kiszka
2008-08-22 14:26     ` Gilles Chanteperdrix
2008-08-22 14:56       ` Jan Kiszka [this message]
2008-08-22 14:59         ` Gilles Chanteperdrix
2008-08-22 15:13           ` Jan Kiszka
2008-08-22 15:20             ` Gilles Chanteperdrix
2008-08-22 15:50               ` Jan Kiszka
2008-08-22 15:55                 ` Gilles Chanteperdrix
2008-08-22 15:56                   ` Jan Kiszka
2008-08-22 16:00                     ` 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=48AED396.3040903@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.