From: Jakub Jelinek <jakub@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, Martin Jambor <mjambor@suse.cz>,
Alexander Monakov <amonakov@ispras.ru>,
Chung-Lin Tang <cltang@codesourcery.com>
Subject: Re: [RFC PATCH] Coalesce host to device transfers in libgomp
Date: Thu, 06 Dec 2018 17:57:00 -0000 [thread overview]
Message-ID: <20181206175731.GU12380@tucnak> (raw)
In-Reply-To: <yxfpwoom8rsj.fsf@hertz.schwinge.homeip.net>
On Thu, Dec 06, 2018 at 06:54:20PM +0100, Thomas Schwinge wrote:
> On Thu, 6 Dec 2018 18:18:56 +0100, Jakub Jelinek <jakub@redhat.com> wrote:
> > On Thu, Dec 06, 2018 at 06:01:48PM +0100, Thomas Schwinge wrote:
> > > While reviewing Chung-Lin's
> > > <https://gcc.gnu.org/ml/gcc-patches/2018-09/msg01428.html> "[PATCH 4/6,
> > > OpenACC, libgomp] Async re-work, libgomp/target.c changes", I noticed the
> > > following unrelated hunk. Is that intentional or just an oversight that
> > > it hasn't been included in your "gomp_coalesce_buf" changes (quoted below
> > > for reference)?
> >
> > I believe it is intentional, the coalescing code coalesces only stuff
> > allocated by the current gomp_map_vars call, for the link_key case we know
> > that is not the case, it is a copy to a file scope data variable in the PTX
> > code.
>
> Hmm, I thought this would just copy an address (as opposed to data) from
> the host to the device, so that would be fine for coalescing. But I'm
> not familiar with that code, so it's certainly possible that I'm not
> understanding this correctly.
The actual data transfer can be coalesced, just the address is copied into
the offloaded file scope var and so that exact transfer can't be coalesced.
> > Perhaps we could do the change but pass NULL instead
> > of cbufp as the last argument?
>
> Like this?
>
> commit 241027a03b70c788ef94ccf258b799332fb1b20e
> Author: Thomas Schwinge <thomas@codesourcery.com>
> Date: Thu Dec 6 18:53:16 2018 +0100
>
> Coalesce host to device transfers in libgomp: not for link pointer
>
> 2018-12-06 Thomas Schwinge <thomas@codesourcery.com>
> Jakub Jelinek <jakub@redhat.com>
>
> libgomp/
> * target.c (gomp_map_vars): Call "gomp_copy_host2dev" instead of
> "devicep->host2dev_func".
Ok for trunk, thanks. Perhaps no need for the "s in the ChangeLog.
> ---
> libgomp/target.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git libgomp/target.c libgomp/target.c
> index 8ebc2a370a16..60f4c96f3908 100644
> --- libgomp/target.c
> +++ libgomp/target.c
> @@ -957,9 +957,11 @@ gomp_map_vars (struct gomp_device_descr *devicep, size_t mapnum,
> /* Set link pointer on target to the device address of the
> mapped object. */
> void *tgt_addr = (void *) (tgt->tgt_start + k->tgt_offset);
> - devicep->host2dev_func (devicep->target_id,
> - (void *) n->tgt_offset,
> - &tgt_addr, sizeof (void *));
> + /* We intentionally do not use coalescing here, as it's not
> + data allocated by the current call to this function. */
> + gomp_copy_host2dev (devicep, (void *) n->tgt_offset,
> + &tgt_addr, sizeof (void *), NULL);
> +
> }
> array++;
> }
Jakub
next prev parent reply other threads:[~2018-12-06 17:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 9:57 Jakub Jelinek
2017-10-24 15:59 ` Cesar Philippidis
2017-10-24 16:02 ` Jakub Jelinek
2017-10-24 17:56 ` Alexander Monakov
2017-10-24 17:40 ` Alexander Monakov
2017-10-24 19:36 ` Jakub Jelinek
2017-10-25 12:03 ` Jakub Jelinek
2017-10-27 14:13 ` [PATCH] Implement omp async support for nvptx Tom de Vries
2017-10-30 7:25 ` Jakub Jelinek
2017-10-30 12:02 ` Tom de Vries
2017-10-30 13:52 ` Tom de Vries
2018-12-06 17:02 ` [RFC PATCH] Coalesce host to device transfers in libgomp Thomas Schwinge
2018-12-06 17:19 ` Jakub Jelinek
2018-12-06 17:54 ` Thomas Schwinge
2018-12-06 17:57 ` Jakub Jelinek [this message]
2018-12-09 12:53 ` Thomas Schwinge
2019-12-18 17:15 ` Thomas Schwinge
2019-05-23 14:40 ` Thomas Schwinge
2019-05-23 14:57 ` Jakub Jelinek
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=20181206175731.GU12380@tucnak \
--to=jakub@redhat.com \
--cc=amonakov@ispras.ru \
--cc=cltang@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mjambor@suse.cz \
--cc=thomas@codesourcery.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 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).