public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Q: stack coherency
Date: Mon, 13 Mar 2000 18:52:17 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678204982@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678204981@msgid-missing>

>>>>> On Sat, 11 Mar 2000 10:02:06 +0100, Manfred Spraul <manfreds@colorfullife.com> said:

  Manfred> Can I access a structure that's stored on the stack of one
  Manfred> CPU from another CPU?

IA-64 is no different in this respect from other architectures.  If
you have an SMP/NUMA/whatever system where the CPUs share the
address-space, you will be able to access the stack of another thread
(assuming the thread's stack is mapped in the address space).  Of
course, you also need to have proper synchronization to ensure the
stack is still live when the second CPU is trying to access it.

I'm not 100% sure what you're asking though, because the "subject"
line of your mail asks about stack coherency.  Coherency is an
orthogonal issue to accessibility.  IA-64 uses a weakly ordered memory
model to achieve high performance.  It's probably best to read the
IA-64 architecture manual for the details (see Section 4.4 at
http://devresource.hp.com/devresource/Docs/Refs/IA64ISA/), but loosely
speaking, memory accesses that happen between a spin-lock/-unlock
pair, will be ordered with respect to accesses by other CPUs.

	--david



      reply	other threads:[~2000-03-13 18:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-11  9:02 [Linux-ia64] Q: stack coherency Manfred Spraul
2000-03-13 18:52 ` David Mosberger [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=marc-linux-ia64-105590678204982@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox