From: "Wiles, Keith" <keith.wiles@intel.com>
To: Kevin Wilson <wkevils@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Minimum kernel version for DPDK
Date: Mon, 20 Aug 2018 12:13:28 +0000 [thread overview]
Message-ID: <8742CC12-28E7-4777-9483-54F1AAEDC1D5@intel.com> (raw)
In-Reply-To: <CAGXs5wXPH4aXwZWcZ=0HO10qmD1tnQQq_t4OKhPxrF35dtK1eA@mail.gmail.com>
> On Aug 20, 2018, at 3:46 AM, 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 ?
I would assume so as long as the kernel has huge page support. If I remember correctly that was one of the big issues with older kernels.
>
> Regards,
> Kevin
Regards,
Keith
next prev parent reply other threads:[~2018-08-20 12:13 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 [this message]
2018-08-20 15:06 ` Stephen Hemminger
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=8742CC12-28E7-4777-9483-54F1AAEDC1D5@intel.com \
--to=keith.wiles@intel.com \
--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).