mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Cleverdon <jamesclv@us.ibm.com>
To: Xuehua Chen <namniardniw@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: A question about cache coherence
Date: Mon, 19 Aug 2002 14:40:23 -0700	[thread overview]
Message-ID: <200208191440.23786.jamesclv@us.ibm.com> (raw)
In-Reply-To: <20020819182121.93059.qmail@web13008.mail.yahoo.com>

On Monday 19 August 2002 11:21 am, Xuehua Chen wrote:
> Met a problem in my research. I run some code on a
> Xeon
> dual-processor machine. It seems to me that there is a
>  cache coherence problem. As I am not so familiar
> to this topic, I would like to ask some experts about
> the following questions.
>
> 1. Do Xeon processors have hardware mechanisms to
> maintain cache coherence?

Someone at Intel can correct me, but I believe they use a modified MESI cache 
coherency protocol.  Note that this coherency does not guarantee indivisible 
read-modify-write operations unless atomic opcodes are used.  (xchg or lock 
<opcode>)

> 2. Does the SMP kernel handle the cache coherence
> problem

See Alan's and others' postings.  The kernel relies on the hardware to keep 
its act straight, then takes care of MMU coherency.

> 3. What should I do if both of them don't handle cache
> coherence.

See 1 and 2.  Consider using futexes or some other mutex mechanism appropriate 
to user or kernel code.

> Thanks.
>
> Frank Samuel

-- 
James Cleverdon
IBM xSeries Linux Solutions
{jamesclv(Unix, preferred), cleverdj(Notes)} at us dot ibm dot com


      parent reply	other threads:[~2002-08-19 21:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-19 18:21 Xuehua Chen
2002-08-19 18:35 ` Matti Aarnio
2002-08-19 19:23 ` Alan Cox
2002-08-19 21:40 ` James Cleverdon [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=200208191440.23786.jamesclv@us.ibm.com \
    --to=jamesclv@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namniardniw@yahoo.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®