DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Lipiec, Herakliusz" <herakliusz.lipiec@intel.com>
To: "jerinj@marvell.com" <jerinj@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 Thomas Monjalon <thomas@monjalon.net>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] config: disable all kmods by default from	v20.02
Date: Wed, 12 Feb 2020 17:18:39 +0000	[thread overview]
Message-ID: <BYAPR11MB29524CA12B4A4E8DDAD3E28AF71B0@BYAPR11MB2952.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200117191400.893118-1-jerinj@marvell.com>

This change also affects usertools/dpdk-setup.sh
When following this: https://doc.dpdk.org/guides/linux_gsg/quick_start.html
And trying to insert igb_uio, it gives following error:

## ERROR: Target does not have the DPDK UIO Kernel Module.
       To fix, please try to rebuild target.

Should this script (and docs) be changed too?

Regards,
Herakliusz

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of jerinj@marvell.com
> Sent: Friday, January 17, 2020 7:14 PM
> To: dev@dpdk.org; Thomas Monjalon <thomas@monjalon.net>; Mcnamara,
> John <john.mcnamara@intel.com>; Kovacevic, Marko
> <marko.kovacevic@intel.com>; Richardson, Bruce
> <bruce.richardson@intel.com>
> Cc: techboard@dpdk.org; Jerin Jacob <jerinj@marvell.com>
> Subject: [dpdk-dev] [PATCH v2] config: disable all kmods by default from
> v20.02
> 
> From: Jerin Jacob <jerinj@marvell.com>
> 
> Based on the techboard meeting held on 2019-11-06, It's been decided to
> disable all kmods by default from v20.02.
> 
> http://mails.dpdk.org/archives/dev/2019-November/151763.html
> 
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> ---
> v2:
> - Updated meson config file to disable the kmods by default(Maxime)
> - Updated the release notes(Honnappa)
> 
> I am not sure, in which section, we need to update the release notes for this
> specific case.I have updated on the "New Features" section.
> Thoughts ?
> 
>  config/common_linux                    | 2 --
>  doc/guides/rel_notes/release_20_02.rst | 5 +++++
>  meson_options.txt                      | 2 +-
>  3 files changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/config/common_linux b/config/common_linux index
> c5cf3d662..583efadc7 100644
> --- a/config/common_linux
> +++ b/config/common_linux
> @@ -8,9 +8,7 @@ CONFIG_RTE_EXEC_ENV_LINUX=y
> CONFIG_RTE_EXEC_ENV_LINUXAPP=y
> 
>  CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=y
> -CONFIG_RTE_EAL_IGB_UIO=y
>  CONFIG_RTE_EAL_VFIO=y
> -CONFIG_RTE_KNI_KMOD=y
>  CONFIG_RTE_LIBRTE_KNI=y
>  CONFIG_RTE_LIBRTE_PMD_KNI=y
>  CONFIG_RTE_LIBRTE_VHOST=y
> diff --git a/doc/guides/rel_notes/release_20_02.rst
> b/doc/guides/rel_notes/release_20_02.rst
> index 9cc257168..afd645e7a 100644
> --- a/doc/guides/rel_notes/release_20_02.rst
> +++ b/doc/guides/rel_notes/release_20_02.rst
> @@ -61,6 +61,11 @@ New Features
>    A new API has been added to wait for a memory location to be updated
> with a
>    16-bit, 32-bit, 64-bit value.
> 
> +* **Disabled all the Linux kernel modules build by default.**
> +
> +  In order to remove the build time dependency with Linux kernel,  The
> + techboard decided to disable all the kernel modules build by  default
> + from v20.02 version.
> 
>  Removed Items
>  -------------
> diff --git a/meson_options.txt b/meson_options.txt index
> bc369d06c..53dfe13c3 100644
> --- a/meson_options.txt
> +++ b/meson_options.txt
> @@ -6,7 +6,7 @@ option('drivers_install_subdir', type: 'string', value:
> 'dpdk/pmds-<VERSION>',
>  	description: 'Subdirectory of libdir where to install PMDs. Defaults to
> using a versioned subdirectory.')  option('enable_docs', type: 'boolean',
> value: false,
>  	description: 'build documentation')
> -option('enable_kmods', type: 'boolean', value: true,
> +option('enable_kmods', type: 'boolean', value: false,
>  	description: 'build kernel modules')
>  option('examples', type: 'string', value: '',
>  	description: 'Comma-separated list of examples to build by default')
> --
> 2.24.1


  parent reply	other threads:[~2020-02-12 17:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12 13:13 [dpdk-dev] [PATCH] " jerinj
2020-01-16 13:11 ` Jerin Jacob
2020-01-16 18:33   ` [dpdk-dev] [dpdk-techboard] " Maxime Coquelin
2020-01-16 18:43     ` Jerin Jacob
2020-01-16 22:38       ` Honnappa Nagarahalli
2020-01-17  4:07         ` Jerin Jacob
2020-01-17 15:48           ` Honnappa Nagarahalli
2020-01-18  0:06             ` Thomas Monjalon
2020-01-17  8:29       ` Maxime Coquelin
2020-01-17  9:19         ` Kevin Traynor
2020-01-17  9:55         ` Jerin Jacob
2020-01-17 19:14 ` [dpdk-dev] [PATCH v2] " jerinj
2020-01-20 17:42   ` Thomas Monjalon
2020-02-12 17:18   ` Lipiec, Herakliusz [this message]
2020-02-12 17:39     ` Thomas Monjalon
2020-01-22  6:34 ` [dpdk-dev] [PATCH] " Stephen Hemminger
2020-01-22  9:08   ` 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=BYAPR11MB29524CA12B4A4E8DDAD3E28AF71B0@BYAPR11MB2952.namprd11.prod.outlook.com \
    --to=herakliusz.lipiec@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=techboard@dpdk.org \
    --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).