DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ranjit Menon <ranjit.menon@intel.com>
To: talshn@mellanox.com, dev@dpdk.org
Cc: thomas@monjalon.net, pallavi.kadam@intel.com,
	dmitry.kozliuk@gmail.com, david.marchand@redhat.com,
	grive@u256.net
Subject: Re: [dpdk-dev] [PATCH 1/7] eal: move OS common functions to single file
Date: Wed, 22 Apr 2020 16:51:56 -0700	[thread overview]
Message-ID: <1248d40a-741d-69ae-a149-4e5b98691f76@intel.com> (raw)
In-Reply-To: <20200422072747.15960-2-talshn@mellanox.com>

On 4/22/2020 12:27 AM, talshn@mellanox.com wrote:
> From: Tal Shnaiderman <talshn@mellanox.com>
> 
> Move common functions between Unix and Windows to eal_config.c.

Like other files in common, we should call this eal_common_config.c

> Those simple functions are getter functions for IOVA, configuration, Multi-process.
> 
> Move rte_config and runtime_dir to be defined in a common file.
> 
> Signed-off-by: Tal Shnaiderman <talshn@mellanox.com>
> ---
>   lib/librte_eal/common/eal_config.c  | 34 ++++++++++++++++++++++++++++++++++
>   lib/librte_eal/common/eal_private.h | 11 +++++++++++
>   lib/librte_eal/common/meson.build   |  2 ++
>   lib/librte_eal/freebsd/eal.c        | 34 ----------------------------------
>   lib/librte_eal/linux/eal.c          | 33 ---------------------------------
>   lib/librte_eal/windows/eal.c        | 36 ------------------------------------
>   6 files changed, 47 insertions(+), 103 deletions(-)
>   create mode 100644 lib/librte_eal/common/eal_config.c
> 
> diff --git a/lib/librte_eal/common/eal_config.c b/lib/librte_eal/common/eal_config.c
> new file mode 100644
> index 000000000..c28080a76
> --- /dev/null
> +++ b/lib/librte_eal/common/eal_config.c
> @@ -0,0 +1,34 @@
> +/* SPDX-License-Identifier: BSD-3-Clause
> + * Copyright(c) 2020 Mellanox Technologies, Ltd
> + */
> +#include <eal_private.h>
> +
> +#include <rte_os.h>
> +
> +/* platform-specific runtime dir */
> +static char runtime_dir[PATH_MAX];
> +
> +const char *
> +rte_eal_get_runtime_dir(void)
> +{
> +	return runtime_dir;
> +}
> +
> +/* Return a pointer to the configuration structure */
> +struct rte_config *
> +rte_eal_get_configuration(void)
> +{
> +	return &rte_config;
> +}
> +
> +enum rte_iova_mode
> +rte_eal_iova_mode(void)
> +{
> +	return rte_eal_get_configuration()->iova_mode;
> +}
> +
> +enum rte_proc_type_t
> +rte_eal_process_type(void)
> +{
> +	return rte_config.process_type;
> +}
> \ No newline at end of file
> diff --git a/lib/librte_eal/common/eal_private.h b/lib/librte_eal/common/eal_private.h
> index 735813d0c..dab9cac1d 100644
> --- a/lib/librte_eal/common/eal_private.h
> +++ b/lib/librte_eal/common/eal_private.h
> @@ -13,6 +13,8 @@
>   #include <rte_lcore.h>
>   #include <rte_memory.h>
>   
> +#include <eal_memcfg.h>
> +
>   /**
>    * Structure storing internal configuration (per-lcore)
>    */
> @@ -60,6 +62,15 @@ struct rte_config {
>   	struct rte_mem_config *mem_config;
>   } __rte_packed;
>   
> +
> +/* early configuration structure, when memory config is not mmapped */
> +static struct rte_mem_config early_mem_config;
> +
> +/* Address of global and public configuration */
> +static struct rte_config rte_config = {
> +		.mem_config = &early_mem_config,
> +};
> +
>   /**
>    * Get the global configuration structure.
>    *
> diff --git a/lib/librte_eal/common/meson.build b/lib/librte_eal/common/meson.build
> index 6dcdcc890..f53a35d0e 100644
> --- a/lib/librte_eal/common/meson.build
> +++ b/lib/librte_eal/common/meson.build
> @@ -20,6 +20,7 @@ if is_windows
>   		'eal_common_options.c',
>   		'eal_common_tailqs.c',
>   		'eal_common_thread.c',
> +		'eal_config.c',
>   		'malloc_elem.c',
>   		'malloc_heap.c',
>   		'rte_malloc.c',
> @@ -52,6 +53,7 @@ sources += files(
>   	'eal_common_thread.c',
>   	'eal_common_timer.c',
>   	'eal_common_uuid.c',
> +	'eal_common.c',

Typo. But, better to rename to eal_common_config.c

>   	'hotplug_mp.c',
>   	'malloc_elem.c',
>   	'malloc_heap.c',

ranjit m.

  reply	other threads:[~2020-04-22 23:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22  7:27 [dpdk-dev] [PATCH 0/7] Windows bus/pci support talshn
2020-04-22  7:27 ` [dpdk-dev] [PATCH 1/7] eal: move OS common functions to single file talshn
2020-04-22 23:51   ` Ranjit Menon [this message]
2020-04-23  7:27     ` Thomas Monjalon
2020-04-23  9:06       ` Dmitry Kozlyuk
2020-04-23 10:48         ` Thomas Monjalon
2020-04-23 16:31           ` Ranjit Menon
2020-04-22  7:27 ` [dpdk-dev] [PATCH 2/7] pci: build on Windows talshn
2020-04-22  7:27 ` [dpdk-dev] [PATCH 3/7] eal: add function finding integer in a string talshn
2020-04-22  7:27 ` [dpdk-dev] [PATCH 4/7] drivers: ignore pmdinfogen generation for Windows talshn
2020-04-22  7:27 ` [dpdk-dev] [PATCH 5/7] drivers: fix incorrect meson import folder " talshn
2020-04-22  7:27 ` [dpdk-dev] [PATCH 6/7] bus/pci: introduce Windows support with stubs talshn
2020-04-22  7:27 ` [dpdk-dev] [PATCH 7/7] bus/pci: support Windows with bifurcated drivers talshn
2020-04-27 22:58   ` Narcisa Ana Maria Vasile
2020-04-28  8:11     ` Tal Shnaiderman

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=1248d40a-741d-69ae-a149-4e5b98691f76@intel.com \
    --to=ranjit.menon@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=grive@u256.net \
    --cc=pallavi.kadam@intel.com \
    --cc=talshn@mellanox.com \
    --cc=thomas@monjalon.net \
    /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).