From: "David S. Miller" <davem@redhat.com>
To: Arun Sharma <arun.sharma@intel.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: SHMLBA and compat tasks
Date: Sat, 28 Feb 2004 15:55:29 -0800 [thread overview]
Message-ID: <20040228155529.64bc0741.davem@redhat.com> (raw)
In-Reply-To: <20040228014128.GA6897@intel.com>
On Fri, 27 Feb 2004 17:41:28 -0800
Arun Sharma <arun.sharma@intel.com> wrote:
> man page:
>
> > If shmaddr isnât NULL and SHM_RND is asserted in shmflg, the attach
> > occurs at the address equal to shmaddr rounded down to the nearest mul-
> > tiple of SHMLBA. Otherwise shmaddr must be a page-aligned address at
> > which the attach occurs.
When the user specifies a specific address, things get real interesting because
of cache aliasing issues.
Platforms with virtually indexed caches use SHMLBA of a size such that
it is the largest cache virtual aliasing factor. In this way, processes
with different SHM mappings of the shared writable memory will immediately
see writes done by other processes and aliases cannot enter the cache due
to virtual addresses being "just right".
Otherwise we'll need to special case now this SHM_RND thing and mark PTE's
as non-cacheable and other horrible things like this, and in fact this particular
scheme is not even possible on some architectures.
So your proposal is going to break things for some people, sparc64, mips, parisc,
and probably a slew of others.
next prev parent reply other threads:[~2004-02-28 23:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 1:41 SHMLBA and compat tasks Arun Sharma
2004-02-28 23:55 ` David S. Miller [this message]
2004-02-29 2:11 ` Arun Sharma
2004-03-01 5:57 ` David S. Miller
2004-03-01 19:33 ` Arun Sharma
2004-03-01 19:41 ` David Mosberger
2004-03-01 20:11 ` David S. Miller
2004-03-01 20:17 ` David Mosberger
2004-03-01 20:16 ` Arun Sharma
2004-03-01 20:55 ` Matthew Wilcox
2004-03-02 19:43 ` Arun Sharma
2004-03-06 2:37 ` Arun Sharma
2004-03-06 7:39 ` David S. Miller
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=20040228155529.64bc0741.davem@redhat.com \
--to=davem@redhat.com \
--cc=arun.sharma@intel.com \
--cc=linux-arch@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