From: "Nicolas König" <koenigni@student.ethz.ch>
To: Iain Sandoe <iain@sandoe.co.uk>, Thomas Koenig <tkoenig@netcologne.de>
Cc: Fortran List <fortran@gcc.gnu.org>, <dhumieres.dominique@free.fr>
Subject: Re: Update on shared memory coarrays
Date: Sat, 2 Jan 2021 23:37:36 +0100 [thread overview]
Message-ID: <adfd839b-b638-b1e8-e335-057864ec99ae@student.ethz.ch> (raw)
In-Reply-To: <6D26C802-E6E0-473F-BB17-A9B373541980@sandoe.co.uk>
Hello Iain,
On 02/01/2021 21:55, Iain Sandoe wrote:
> Thomas Koenig via Fortran <fortran@gcc.gnu.org> wrote:
>
>>> map_memory image 0 size 1000 offset 0 pagesize 1000
>>> map_memory image 0 size 2000 offset 0 pagesize 1000
>
> pagesize 1000?
Pretty sure that's hex :)
>
> Darwin’s pagesize is 4096 for PPC/X86 and 16384 for Arm64(aarch64).
>
>>> mmap failed: Invalid argument
>>
>> That means that a rewrite of shared_memory.c and shared_memory.h
>> is required.
>>
>> I checked the attached program on every Unixoid system I
>> could lay my hands on (Linux, AIX, OpenBSD, NetBSD, FreeBSD,
>> OpenSolaris), and it passed everywhere. Seems like MacOS
>> is the only one where this particular idiom does not work.
>
> Perhaps I’m missing what the idiom is here :)
At the moment, we are double-mapping pages in the shared_memory. This
was on the list of things that should be changed, but according to
Thomas's tests, you can't do this on MacOS, so it just got a whole lot
more important.
Nicolas
>
> (a bit tied up with other things at the moment so mainly watching from
> the peanut gallery for now)
>
> Iain
>
next prev parent reply other threads:[~2021-01-02 21:38 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 19:09 dhumieres.dominique
2020-11-30 6:21 ` Thomas Koenig
2020-11-30 15:41 ` dhumieres.dominique
2020-11-30 22:13 ` Thomas Koenig
2020-12-02 17:41 ` dhumieres.dominique
2020-12-03 7:27 ` Thomas Koenig
2020-12-21 12:24 ` dhumieres.dominique
2020-12-21 13:04 ` Thomas Koenig
2020-12-22 12:28 ` dhumieres.dominique
2020-12-22 15:10 ` Thomas Koenig
2020-12-22 16:12 ` Paul Richard Thomas
2020-12-23 9:09 ` Thomas Koenig
2020-12-23 9:38 ` Paul Richard Thomas
2020-12-23 10:47 ` Thomas Koenig
2020-12-26 12:10 ` Paul Richard Thomas
2020-12-26 13:01 ` Thomas Koenig
2020-12-27 15:38 ` Thomas Koenig
2020-12-23 16:42 ` Nicolas König
2020-12-23 17:25 ` dhumieres.dominique
2020-12-27 17:10 ` Nicolas König
2021-01-01 13:51 ` dhumieres.dominique
2021-01-01 16:16 ` Thomas Koenig
2021-01-01 16:41 ` dhumieres.dominique
2021-01-02 20:45 ` Thomas Koenig
2021-01-02 20:55 ` Iain Sandoe
2021-01-02 21:43 ` Thomas Koenig
2021-01-02 22:37 ` Nicolas König [this message]
2021-01-02 21:44 ` Iain Sandoe
2021-01-02 22:09 ` Iain Sandoe
2021-01-03 10:46 ` Iain Sandoe
2021-01-03 14:54 ` Iain Sandoe
2021-01-03 15:42 ` Iain Sandoe
2021-01-03 21:53 ` Thomas Koenig
2021-01-04 2:34 ` Iain Sandoe
2021-01-04 18:54 ` Nicolas König
2021-01-05 13:11 ` Iain Sandoe
2021-01-05 13:23 ` Iain Sandoe
2021-01-05 13:27 ` Thomas Koenig
2021-01-05 13:34 ` Iain Sandoe
2021-01-05 14:54 ` Nicolas König
2021-01-05 14:28 ` Iain Sandoe
2021-01-05 15:45 ` Nicolas König
[not found] ` <BAD6EA1D-BB9F-4905-ADD1-76FA1D6B9591@sandoe.co.uk>
2021-01-05 17:11 ` Nicolas König
2021-01-06 16:56 ` Iain Sandoe
-- strict thread matches above, loose matches on Subject: below --
2020-11-29 13:10 Nicolas König
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=adfd839b-b638-b1e8-e335-057864ec99ae@student.ethz.ch \
--to=koenigni@student.ethz.ch \
--cc=dhumieres.dominique@free.fr \
--cc=fortran@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=tkoenig@netcologne.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).