From: Bruce Richardson <bruce.richardson@intel.com>
To: hamidreza Kheirabadi <hamidreza.kheirabadi@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] dpdk-20.11 is really released as LTS?
Date: Tue, 9 Feb 2021 11:55:30 +0000 [thread overview]
Message-ID: <20210209115530.GB1208@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAKtNQLjKt_PuOwhZ-R1KN9sdj-9QLGbG8fXXnB2NhY8qY+agcg@mail.gmail.com>
On Tue, Feb 09, 2021 at 02:25:19PM +0330, hamidreza Kheirabadi wrote:
> Hi,
> I used previous versions of dpdk (like 18.05) in my project very well.
> Recently I decided to migrate to 20.11 but I have lots of problems with it.
> I built it with meson and ninja as described in docs but no .ko has been
> built.
The kernel modules are no longer built by default, and the igb_uio module
has been moved out of the main repository to a separate one. For igb_uio,
it is recommended you use vfio-pci module from the upstream kernel instead
(it's included in all major Linux distro kernel's by default, so no
additional compile necessary). For kni module, if that is a module you use,
configure meson with "-Denable_kmods=true", and it will be built.
> The structure of examples also changed and was replaced by a single
> huge file. Is it really tested and published as LTS?
Not sure what you mean about the structure of the examples. Their directory
layout is largely the same as what it was, only the way in which they are
built is now a little different (as with the rest of DPDK).
/Bruce
prev parent reply other threads:[~2021-02-09 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 10:55 hamidreza Kheirabadi
2021-02-09 11:55 ` Bruce Richardson [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=20210209115530.GB1208@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hamidreza.kheirabadi@gmail.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).