From: Iain Sandoe <iain@sandoe.co.uk>
To: "Thomas Koenig" <tkoenig@netcologne.de>,
"Nicolas König" <koenigni@student.ethz.ch>
Cc: "dhumieres.dominique@free.fr" <dhumieres.dominique@free.fr>,
Fortran List <fortran@gcc.gnu.org>
Subject: Re: Update on shared memory coarrays
Date: Tue, 5 Jan 2021 13:23:16 +0000 [thread overview]
Message-ID: <34D664D7-1A03-4DD6-9309-36F6D8A30060@sandoe.co.uk> (raw)
In-Reply-To: <816E309C-4983-4159-973D-F1A46AD8CB3C@sandoe.co.uk>
Iain Sandoe <iain@sandoe.co.uk> wrote:
> Update:
>
> three codes attached.
>
> 1. Posix shm implementation; works fine but is not resizeable.
>
> 2. Darwin shm implementation : works fine but is only resizable downwards
> and it’s not clear if the resources are actually released.
>
> 3. mmapped shared file : This works [on Darwin at least] and is resizable.
> I would assume that, in reality, all accesses would be to the buffer cache
> [unless something actually forces the cache to be flushed] and therefore
> that the performance ought to be similar to shm.
>
> Worst case, one could point /tmp at a ramdisk ..
> (I tend to do that anyway, I don’t want my sshds getting hammered by
> toolchain builds).
>
> <shm-posix.c><shm-darwin.c><ram-file.c>
… I omitted :
gcc <file> -DSENDER -o A
gcc <file> -o B
(output for the working case, ram-file)
A &
sender page size = 4096
get_shared_resource: fd = 3
sender resource pointer = 0x0x103d1b000
B &
client page size = 4096
get_shared_resource: fd = 3
client resource pointer = 0x0x10e3a7000
client saw 42, resizing now
client resized resource pointer = 0x0x10e3a7000
sender saw -42, resizing now
sender resized resource pointer = 0x0x103d1b000
sender sees 6174
next prev parent reply other threads:[~2021-01-05 13:23 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
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 [this message]
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=34D664D7-1A03-4DD6-9309-36F6D8A30060@sandoe.co.uk \
--to=iain@sandoe.co.uk \
--cc=dhumieres.dominique@free.fr \
--cc=fortran@gcc.gnu.org \
--cc=koenigni@student.ethz.ch \
--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).