From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: James Huang <jamsphon@gmail.com>
Cc: users@dpdk.org, "Wiles, Keith" <keith.wiles@intel.com>
Subject: Re: [dpdk-users] DPDK Linux kernel version requirement
Date: Fri, 18 Nov 2016 09:16:42 +0100 [thread overview]
Message-ID: <2288577.64UbDlIlDh@xps13> (raw)
In-Reply-To: <CAFpuyR4kNJuJFmzJG252ry8vnO0FviA_KOFD=TEPKHk4B7Vztg@mail.gmail.com>
2016-11-17 11:46, James Huang:
> CentOS release 6.5 (Final)
[...]
> According to the test results, could I say DPDK 32bit applications are
> GOOD to run on Linux 64bit kernel v2.6.32?
CentOS has a lot of backports so it is not really a 2.6.32 kernel.
It is good to know that DPDK 16.07 runs on CentOS 6.5,
but we cannot conclude on other 2.6.32 distributions.
next prev parent reply other threads:[~2016-11-18 8:16 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 [this message]
2016-11-18 17:45 ` 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=2288577.64UbDlIlDh@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=jamsphon@gmail.com \
--cc=keith.wiles@intel.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).