DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hamed khanmirza <hamedkh@gmail.com>
To: Daniel Kaminsky <daniel.kaminsky@infinitelocality.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Selecting Linux distribution for DPDK applications: CentOS or Debian
Date: Thu, 30 Jan 2014 17:36:04 +0330	[thread overview]
Message-ID: <CALSoDghMKizw9a-M7m86oqKvzLDqWm47a+1RknMAfd0KYWto4g@mail.gmail.com> (raw)
In-Reply-To: <CA+8v-JxV=F_3NfgRYxu+ziHS3+r3XtxfEqk1f4B97NS-yHJC-w@mail.gmail.com>

Hi Dan,

We are also using Debian 7.3, from the DPDK v1.3.1 up to version 1.5.1r1.
it works completely fine.

regards,
- Hamed


On Thu, Jan 30, 2014 at 3:40 PM, Daniel Kaminsky <
daniel.kaminsky@infinitelocality.com> wrote:

> We're using CentOS 6.5 and Ubuntu 12.04 and don't see any issue with both
> of them.
>
> Regards,
> Daniel Kaminsky
>
>
> On Thu, Jan 30, 2014 at 12:12 PM, Prashant Upadhyaya <
> prashant.upadhyaya@aricent.com> wrote:
>
> > 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.
> >
> >
> ===============================================================================
> >
>

  reply	other threads:[~2014-01-30 14:05 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
2014-01-30 12:10   ` Daniel Kaminsky
2014-01-30 14:06     ` Hamed khanmirza [this message]
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=CALSoDghMKizw9a-M7m86oqKvzLDqWm47a+1RknMAfd0KYWto4g@mail.gmail.com \
    --to=hamedkh@gmail.com \
    --cc=daniel.kaminsky@infinitelocality.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).