From: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
To: Daniel Kan <dan@nyansa.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Selecting Linux distribution for DPDK applications: CentOS or Debian
Date: Thu, 30 Jan 2014 15:42:26 +0530 [thread overview]
Message-ID: <C7CE7EEF248E2B48BBA63D0ABEEE700C5A2A24F976@GUREXMB01.ASIAN.AD.ARICENT.COM> (raw)
In-Reply-To: <886FB96F-B46C-4129-A609-D80E5D1B2B5E@nyansa.com>
Hi Dan,
Intel DPDK release notes(1.5.2) mention the following tested OS --
* Fedora release 18
* Ubuntu* 12.04 LTS
* Wind River* Linux* 5
* Red Hat* Enterprise Linux 6.3
* SUSE Enterprise Linux* 11 SP2
I have personally used Fedora 18 and it works fine for me for virtualization including SRIOV and pass through as well as virtio with KNI backend.
So I am tending to stick to Fedora 18.
I don't know why is CentOS not tested and mentioned in release notes.
Regards
-Prashant
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Daniel Kan
Sent: Thursday, January 30, 2014 2:01 PM
To: dev@dpdk.org
Subject: [dpdk-dev] Selecting Linux distribution for DPDK applications: CentOS or Debian
I'm deciding between Debian 7.3 (3.2.0 kernel) and CentOS 6.5 (2.6.32 kernel) for production. I'm wondering if anyone has recommendation. We run the DPDK application in a virtualized environment. Currently, we configure NICs in pass-through mode which gives the best performance. In the future, we plan to use DPDK with paravirtualized nics (eg. vmxnet3-usermap). Thanks.
Dan
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
next prev parent reply other threads:[~2014-01-30 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 8:30 Daniel Kan
2014-01-30 10:12 ` Prashant Upadhyaya [this message]
2014-01-30 12:10 ` Daniel Kaminsky
2014-01-30 14:06 ` Hamed khanmirza
2014-01-30 19:32 ` Daniel Kan
2014-01-30 19:39 ` Selvaganapathy Chidambaram
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=C7CE7EEF248E2B48BBA63D0ABEEE700C5A2A24F976@GUREXMB01.ASIAN.AD.ARICENT.COM \
--to=prashant.upadhyaya@aricent.com \
--cc=dan@nyansa.com \
--cc=dev@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).