From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Luke Kenneth Casson Leighton <luke.leighton@gmail.com>
Cc: paulmck@linux.vnet.ibm.com, Will Newton <will.newton@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: advice sought: practicality of SMP cache coherency implemented in assembler (and a hardware detect line)
Date: Mon, 28 Mar 2011 23:18:18 +0100 [thread overview]
Message-ID: <20110328231818.2297408f@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <AANLkTin6kg84P50RHR7h6NG+P_nJK=N_Nefc1q4NxzY_@mail.gmail.com>
> ok - well, having thought about this a little bit (in a non-detailed
> high-level way) i was sort-of hoping, as alan hinted at, to still do
> SMP, even if it's slow, for userspace. the primary thing to prevent
> from happening is to have kernelspace data structures from
> conflicting.
>
> i found kerrigan, btw, spoke to the people on it: louis agreed that
> the whole idea was mad as hell and was therefore actually very
> interesting to attempt :)
>
> as a first approximation i'm absolutely happy for existing pthreads
> applications to be forced to run on the same core.
The underlying problem across a cluster of nodes can be handled
transparently. MOSIX solved that problem a very long time ago using DSM
(distributed shared memory). It's not pretty, it requires a lot of tuning
to make it fly but they did it over comparatively slow interconnects.
Alan
next prev parent reply other threads:[~2011-03-28 22:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 21:52 Luke Kenneth Casson Leighton
2011-03-25 22:41 ` Will Newton
2011-03-26 12:08 ` Alan Cox
2011-03-28 18:06 ` Paul E. McKenney
2011-03-28 18:48 ` Luke Kenneth Casson Leighton
2011-03-28 22:12 ` Paul E. McKenney
2011-03-28 22:18 ` Alan Cox [this message]
2011-03-28 23:38 ` Luke Kenneth Casson Leighton
2011-03-28 23:39 ` Luke Kenneth Casson Leighton
2011-03-28 23:53 ` Paul E. McKenney
2011-03-29 9:16 ` Alan Cox
2011-04-07 12:09 ` Luke Kenneth Casson Leighton
2011-04-08 16:24 ` Paul E. McKenney
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=20110328231818.2297408f@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luke.leighton@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=will.newton@gmail.com \
/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
all inboxes | Powered by JetHome®