DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Srikanth Yalavarthi <syalavarthi@marvell.com>
Cc: Ray Kinsella <mdr@ashroe.eu>, <dev@dpdk.org>,
	<jerinj@marvell.com>, <sshankarnara@marvell.com>
Subject: Re: [PATCH v5 1/1] eal: add internal function to get base address
Date: Fri, 4 Feb 2022 22:28:47 +0300	[thread overview]
Message-ID: <20220204222847.09eb77ac@sovereign> (raw)
In-Reply-To: <20220118133340.25225-1-syalavarthi@marvell.com>

2022-01-18 05:33 (UTC-0800), Srikanth Yalavarthi:
> Added an internal helper to get OS-specific EAL mapping base address
> 
> This helper can be used by the drivers to program offload / accelerator
> devices, where the base address can be used as a reference address by
> the accelerator to access the host memory
> 
> An address can also be represented as an offset relative to the base
> address using smaller data types
> 
> Signed-off-by: Srikanth Yalavarthi <syalavarthi@marvell.com>
> ---
>  lib/eal/common/eal_common_config.c | 9 +++++++++
>  lib/eal/include/rte_eal.h          | 9 +++++++++
>  lib/eal/version.map                | 1 +
>  3 files changed, 19 insertions(+)

Acked-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>

  parent reply	other threads:[~2022-02-04 19:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 11:22 [PATCH " Srikanth Yalavarthi
2022-01-17 13:38 ` [PATCH v3 " Srikanth Yalavarthi
2022-01-17 13:42 ` [PATCH v4 " Srikanth Yalavarthi
2022-01-17 14:43   ` Dmitry Kozlyuk
2022-01-18  5:29     ` [EXT] " Srikanth Yalavarthi
2022-01-18  9:40       ` Dmitry Kozlyuk
2022-01-18 13:33 ` [PATCH v5 " Srikanth Yalavarthi
2022-02-02 14:19   ` Thomas Monjalon
2022-02-04 19:28   ` Dmitry Kozlyuk [this message]
2022-02-08 17:15   ` Burakov, Anatoly
2022-02-08 22:58     ` Thomas Monjalon

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=20220204222847.09eb77ac@sovereign \
    --to=dmitry.kozliuk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=mdr@ashroe.eu \
    --cc=sshankarnara@marvell.com \
    --cc=syalavarthi@marvell.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).