DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Elena Agostini <eagostini@nvidia.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2] gpudev: use CPU map functionality in comm list
Date: Tue, 22 Feb 2022 19:46:44 +0100	[thread overview]
Message-ID: <2265539.1SvkZsmPdQ@thomas> (raw)
In-Reply-To: <20220222002233.21076-1-eagostini@nvidia.com>

22/02/2022 01:22, eagostini@nvidia.com:
> From: Elena Agostini <eagostini@nvidia.com>
> 
> rte_gpu_mem_cpu_map() exposes a GPU memory area to the CPU.
> In gpudev communication list this is useful to store the
> status flag.
> 
> A communication list status flag allocated on GPU memory
> and mapped for CPU visibility can be updated by CPU and polled
> by a GPU workload.
> 
> The polling operation is more frequent than the CPU update operation.
> Having the status flag in GPU memory reduces the GPU workload polling
> latency.
> 
> If CPU mapping feature is not enabled, status flag resides in
> CPU memory registered so it's visible from the GPU.
> 
> To facilitate the interaction with the status flag, this patch
> provides also the set/get functions for it.
> 
> Signed-off-by: Elena Agostini <eagostini@nvidia.com>

[...]
>   * @param ptr
> - *   Pointer to the GPU memory area to be unmapped.
> + *   Pointer to the memory area to be unmapped.

rebase issue: that reverts another commit sent the same day. I will skip

[...]
>  #endif /* RTE_GPUDEV_H */
> +

Will remove lines added at the end of 2 files.

Applied, thanks.



      reply	other threads:[~2022-02-22 18:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22  0:17 [PATCH v1] " eagostini
2022-02-22  0:22 ` [PATCH v2] " eagostini
2022-02-22 18:46   ` Thomas Monjalon [this message]

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=2265539.1SvkZsmPdQ@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=eagostini@nvidia.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 NNTP newsgroup(s).