DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] UIO RTE_INTR_MODE_NONE issue.
Date: Mon, 6 Jul 2015 10:36:31 -0700	[thread overview]
Message-ID: <20150706103631.3788f969@urahara> (raw)
In-Reply-To: <1791248.rusHJ6L7fN@xps13>

On Sat, 04 Jul 2015 14:36:15 +0200
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:

> Hi Stephen,
> 
> 2015-07-03 12:58, Stephen Hemminger:
> > PPS: With DPDK 2.2 it would be good to move the minimum kernel version up to 3.0
> > since that is what current stable distro's are using.
> 
> Yes, this is something to consider.
> Please send a doc patch to open the discussion.

Something like??


diff --git a/doc/guides/rel_notes/faq.rst b/doc/guides/rel_notes/faq.rst
index d87230a..715a03c 100644
--- a/doc/guides/rel_notes/faq.rst
+++ b/doc/guides/rel_notes/faq.rst
@@ -175,6 +175,9 @@ Any kernel greater than version 2.6.33 can be used without any patches applied.
 
         (not mandatory, but recommended on a NUMA system to support per-NUMA node hugepages allocation)
 
+If starting a new project it worth using the latest stable version of a distribution.
+The next version of the DPDK 2.2 will require kernel version 3.0 or later.
+
 .. note::
 
     Blue text in the lists above are direct links to the patch downloads.

  reply	other threads:[~2015-07-06 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 10:07 Prathap T
2015-07-03 22:58 ` Stephen Hemminger
2015-07-04  3:34   ` Prathap Thammanna
2015-07-04 12:36   ` Thomas Monjalon
2015-07-06 17:36     ` Stephen Hemminger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-02  3:23 Prathap Thammanna

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=20150706103631.3788f969@urahara \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).