DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: James Huang <jamsphon@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] DPDK Linux kernel version requirement
Date: Fri, 18 Nov 2016 09:45:13 -0800	[thread overview]
Message-ID: <20161118094513.509019a4@samsung9> (raw)
In-Reply-To: <CAFpuyR5b26BVYYFkozeXNw9it42C1DoUS59hJdNO2KH7gGeKog@mail.gmail.com>

On Thu, 17 Nov 2016 10:27:49 -0800
James Huang <jamsphon@gmail.com> wrote:

> Hi,
> 
> Nice to join DPDK community.
> 
> read from DPDK system requirements for Linux
> (http://dpdk.org/doc/guides/linux_gsg/sys_reqs.html)
> 
>   Kernel version >= 2.6.34
> 
> I'd like to know if there is any reason to block DPDK build and run on
> older kernel version, i.e. 2.6.32, as carried on CentOS 6. where
> gcc=4.4.
> 
> Could we just keep our CentOS 6 64bit x86_64 OS and continuing running
> 32bit applications with DPDK injected.
> 
> or, there are good reasons *must* upgrade to CentOS 7, where
> kernel=3.10.0, gcc=4.8, and re-build applications to 64bit as well?
> 
> Thanks a lot!
> 
> 
> James

There are kernel modules, and the DPDK developers have no incentive
do do all the back porting to older kernels. I suspect newer releases
will require 3.2 or later soon.

      parent reply	other threads:[~2016-11-18 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 18:27 James Huang
2016-11-17 18:32 ` Wiles, Keith
2016-11-17 19:46   ` James Huang
2016-11-18  8:16     ` Thomas Monjalon
2016-11-18 17:45 ` 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=20161118094513.509019a4@samsung9 \
    --to=stephen@networkplumber.org \
    --cc=jamsphon@gmail.com \
    --cc=users@dpdk.org \
    /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).