From: Jun Sun <jsun@mvista.com>
To: Atsushi Nemoto <nemoto@toshiba-tops.co.jp>
Cc: turcotte@broadcom.com, linux-mips@oss.sgi.com, mturc@broadcom.com
Subject: Re: Linux Shared Memory Issue
Date: Thu, 25 Apr 2002 11:46:04 -0700 [thread overview]
Message-ID: <3CC84EEC.8060100@mvista.com> (raw)
In-Reply-To: 20020425.142518.85417141.nemoto@toshiba-tops.co.jp
Atsushi Nemoto wrote:
>>>>>>On Wed, 24 Apr 2002 15:03:15 -0700, Jun Sun <jsun@mvista.com> said:
>>>>>>
> jsun> Looks like the infamous cache aliasing problem. Steve
> jsun> Longerbeam had a patch which may help. Please try it and let me
> jsun> know the results.
>
> jsun> +#define COLOUR_ALIGN(addr) (((addr)+SHMLBA-1)&~(SHMLBA-1))
>
> Recent sparc64's COLOUR_ALIGN macro have pgoff argument like this.
> We should do it same way for MIPS?
>
> #define COLOUR_ALIGN(addr,pgoff) \
> ((((addr)+SHMLBA-1)&~(SHMLBA-1)) + \
> (((pgoff)<<PAGE_SHIFT) & (SHMLBA-1)))
>
What is the purpose of adding the pgoff part? To avoid mapping all shared
regions into the beginning of cache?
Jun
next prev parent reply other threads:[~2002-04-25 19:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 21:27 Linux Shared Memory Issue Maurice Turcotte
2002-04-24 22:03 ` Jun Sun
2002-04-25 5:25 ` Atsushi Nemoto
2002-04-25 18:46 ` Jun Sun [this message]
2002-04-26 3:11 ` Atsushi Nemoto
2002-04-27 21:45 ` XSHM/shared-pixmap fix Was: " Florian Lohoff
2002-05-06 11:04 ` Maciej W. Rozycki
2002-04-25 15:36 ` Florian Lohoff
-- strict thread matches above, loose matches on Subject: below --
2001-08-06 7:44 SysV IPC shared memory and virtual alising Atsushi Nemoto
2001-08-06 8:50 ` Dominic Sweetman
2001-08-14 8:24 ` Ralf Baechle
2001-08-14 8:49 ` Ralf Baechle
2001-08-16 3:04 ` Atsushi Nemoto
2002-05-07 6:48 ` XSHM/shared-pixmap fix Was: Linux Shared Memory Issue Atsushi Nemoto
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=3CC84EEC.8060100@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=mturc@broadcom.com \
--cc=nemoto@toshiba-tops.co.jp \
--cc=turcotte@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.