From: Stephen Hemminger <stephen@networkplumber.org>
To: Kevin Wilson <wkevils@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Minimum kernel version for DPDK
Date: Mon, 20 Aug 2018 08:06:36 -0700 [thread overview]
Message-ID: <20180820080636.2d77daeb@xeon-e3> (raw)
In-Reply-To: <CAGXs5wXPH4aXwZWcZ=0HO10qmD1tnQQq_t4OKhPxrF35dtK1eA@mail.gmail.com>
On Mon, 20 Aug 2018 11:46:25 +0300
Kevin Wilson <wkevils@gmail.com> wrote:
> Hi all,
> Maybe this is a silly question, please bear with me.
>
> According to the “Getting Started Guide for Linux” in
> http://doc.dpdk.org/guides/linux_gsg/sys_reqs.html,
> the kernel version should be >= 3.2.
> Accrding to my understanding, there are only two kernel modules in DPDK,
> namely rte_kni.ko and igb_iuo.ko.
> Instead of igb_uio.ko I intend to use uio_pci_generic.ko for binding the device.
>
> I want to work with DPDK with kernel 3.1, without using rte_kni and no igb_uio
> as mentioned.
>
> Won't the DPDK code compile for such a kernel ? won't it work ?
>
> Regards,
> Kevin
I would never build and deploy an application a kernel older than
the current Long Term Supported kernel (3.16). If you are an unsupported
kernel, you put yourself at risk of the next big security attack.
If you are selling a product, then using older kernels is just
asking it to be pawned.
prev parent reply other threads:[~2018-08-20 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 8:46 Kevin Wilson
2018-08-20 12:13 ` Wiles, Keith
2018-08-20 15:06 ` Stephen Hemminger [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=20180820080636.2d77daeb@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=wkevils@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).