Hi Dmitry, This is to cater to use cases where chunks of memory are allocated by the host / application, and would like to represent it as an offset from the Linux virtual base address. One use case is for a firmware running on an accelerator, this can be used as reference address to access host memory.
Another situation can be to use the offset as an identifier for the memory using smaller data types Srikanth -----Original Message----- From: Dmitry Kozlyuk <dmitry.kozl...@gmail.com> Sent: 17 January 2022 20:14 To: Srikanth Yalavarthi <syalavar...@marvell.com> Cc: Ray Kinsella <m...@ashroe.eu>; dev@dpdk.org; Jerin Jacob Kollanukkaran <jer...@marvell.com>; Shivah Shankar Shankar Narayan Rao <sshankarn...@marvell.com> Subject: [EXT] Re: [PATCH v4 1/1] eal: add internal function to get base address External Email ---------------------------------------------------------------------- 2022-01-17 05:42 (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 map host address range with > offload devices and would be need for device specific operations like > firmware load Hello Srikanth, Please elaborate on the intended usage of the new API and how it will correlate with the EAL usage of the same VA ranges. Note that on Windows eal_get_baseaddr() returns 0 which does not imply anything about where EAL mappings will reside.
