public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: [RFC] NUMA functions for accessing replicated areas
Date: Sun, 20 Jan 2002 00:15:18 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805891@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805887@msgid-missing>

On Sat, 19 Jan 2002 18:02:20 -0600 (CST), 
Jack Steiner <steiner@sgi.com> wrote:
>There is one thing that occurred to me. Currently, on IA64, the replicated
>data is read-execute. The NUMA code known how to write it but I dont
>know if you want to teach kdb how to do it.

That is exactly what I don't want to do.  I want numa_putarea_size to
take a virtual target address and copy the data to all instances of
that target address.  kdb should not know about translating one to
many, the numa functions hide that complexity from anything that needs
to update replicated data.



      parent reply	other threads:[~2002-01-20  0:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-19 17:27 [Linux-ia64] Re: [RFC] NUMA functions for accessing replicated areas Andrea Arcangeli
2002-01-19 22:35 ` Keith Owens
2002-01-20  0:15 ` Keith Owens [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-105590698805891@msgid-missing \
    --to=kaos@sgi.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