From: Bill Davidsen <davidsen@tmr.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: microblaze-uclinux@itee.uq.edu.au
Subject: Re: Microblaze - The fist year
Date: Sun, 09 May 2010 12:49:31 -0400 [thread overview]
Message-ID: <4BE6E79B.5080608@tmr.com> (raw)
In-Reply-To: <4BC57478.3080902@lumino.de>
Michael Schnell wrote:
> On 04/13/2010 03:27 PM, Michal Simek wrote:
>>
>> yes, futex is there. You can check it in
>> arch/microblaze/include/asm/futex.h
> Great ! I'll check how this is done.
>>
>>> Does Microblaze MMU Linux support SMP ?
>>
>> It is possible to connect several MicroBlazes but the problem is
>> missing cache coherency modul. I hope that Xilinx will release any
>> version which will support it.
>> We haven't done any significant work to support it but it is expected
>> solution which will happen.
>
> Besides cache coherency, another problem might be doing FUTEX. here (I
> suppose) SMP safe atomic user space operations are necessary. many
> simple RISK (load/store-) CPUs don't provide these (new ARMs provide
> "load-locked / store-conditional" on that behalf as an extension to the
> load/store paradigm. I suppose these can be done in an SMP-safe way,
> supposedly using the hardware that provides cache coherency).
>
I wonder if you could make this work with some variant of NUMA
configuration. I don't predict anything about being practical even if it
works, just a thought.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
prev parent reply other threads:[~2010-05-09 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 12:21 Microblaze - The fist year Michal Simek
2010-04-13 13:12 ` Michael Schnell
2010-04-13 13:27 ` Michal Simek
2010-04-14 7:53 ` Michael Schnell
2010-05-09 16:49 ` Bill Davidsen [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=4BE6E79B.5080608@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
/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