From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [PATCH v2 1/3] nucleus: Use Linux spin lock for heap list management
Date: Mon, 19 Oct 2009 21:10:55 +0200 [thread overview]
Message-ID: <4ADCB9BF.5090604@domain.hid> (raw)
In-Reply-To: <4ADCAB36.8080103@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> No need for hard nklock protection of kheapq and the map counter, a
>> normal spin lock suffices as all users must run over the root thread
>> anyway.
>
> At the very least, this should use rthal_spin_lock, in order to seem to
> respect the layering.
Then the conversion would make no sense (hard interrupt lock again).
Given that we are fiddling with Linux mm directly here, there is no hal
involved.
>
> Anyway, do we really want to change this now?
>
That's a different question. The patch alone does not buy us that much
when we cannot reuse the lock for the heapq.
Jan
PS: More invasive changes will come anyway to plug cleanup races in the
heap code.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-10-19 19:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 17:16 [Xenomai-core] [PATCH v2 0/3] Sem heap statistics & mutex auto-cleanup fixes Jan Kiszka
2009-10-19 17:16 ` [Xenomai-core] [PATCH v2 2/3] nucleus: Include all heaps in statistics Jan Kiszka
2009-10-19 18:17 ` Gilles Chanteperdrix
2009-10-19 19:09 ` Jan Kiszka
2009-10-20 10:32 ` Philippe Gerum
2009-10-20 11:44 ` Jan Kiszka
2009-10-20 12:48 ` Philippe Gerum
2009-10-19 17:16 ` [Xenomai-core] [PATCH v2 3/3] native: Release fastlock to the proper heap Jan Kiszka
2009-10-19 17:16 ` [Xenomai-core] [PATCH v2 1/3] nucleus: Use Linux spin lock for heap list management Jan Kiszka
2009-10-19 18:08 ` Gilles Chanteperdrix
2009-10-19 19:10 ` Jan Kiszka [this message]
2009-10-19 19:17 ` 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=4ADCB9BF.5090604@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.