mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Robert Schwebel" <r.schwebel@pengutronix.de>
Cc: "Mathieu Desnoyers" <mathieu.desnoyers@polymtl.ca>,
	tonyko@lineo.ca, robin.getz@analog.com,
	linux-kernel@vger.kernel.org
Subject: Re: blackfin - cmpxchg not atomic ?
Date: Sat, 21 Jul 2007 04:37:35 -0400	[thread overview]
Message-ID: <8bd0f97a0707210137j186554b6tb22e7f36237e862f@mail.gmail.com> (raw)
In-Reply-To: <20070721072930.GS1678@pengutronix.de>

On 7/21/07, Robert Schwebel <r.schwebel@pengutronix.de> wrote:
> On Fri, Jul 20, 2007 at 04:36:12PM -0400, Mike Frysinger wrote:
> > > Also, does you assembly stub _really_ modify memory atomically ? If yes,
> > > then there should be no need for disabling interrupts. Else, I see a
> > > major problem with SMP.
> >
> > that isnt the only problem with SMP on Blackfin
>
> Could you ealborate?

i'm pretty sure there's already been a thread on LKML about it ... the
fact that our parts currently lack any sort of cache snooping or
control over any other is a huge issue.

we've contracted a company to do SMP, but it'll have quite a bit of
overhead since it'll need to do a lot of communication/message passing
between cores to account for these hardware deficiencies.
-mike

  reply	other threads:[~2007-07-21  8:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 20:28 Mathieu Desnoyers
2007-07-20 20:36 ` Mike Frysinger
2007-07-20 20:45   ` Mathieu Desnoyers
2007-07-20 20:59     ` Mike Frysinger
2007-07-21  7:29   ` Robert Schwebel
2007-07-21  8:37     ` Mike Frysinger [this message]
2007-07-23 17:24 ` Robin Getz

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=8bd0f97a0707210137j186554b6tb22e7f36237e862f@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=r.schwebel@pengutronix.de \
    --cc=robin.getz@analog.com \
    --cc=tonyko@lineo.ca \
    /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®