DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] Fixed/Simplified Ring PMD
Date: Wed,  9 Jul 2014 15:35:34 +0100	[thread overview]
Message-ID: <1404916536-1364-1-git-send-email-pablo.de.lara.guarch@intel.com> (raw)

Ring PMD library and unit test was modified last release,
causing the unit test to need ring ethdevs to be created
from the command line. This patch simplifies the test
and make it functional with devices created with EAL option vdev.

Also, ring ethdev creation from vdev has been changed, so now
only one device is created for each vdev argument (up to 3 devices
were created). 


Pablo de Lara (2):
  ring_pmd: Removed extra devices creation when passing vdev parameter
  app/test: Simplified ring pmd test

 app/test/test_pmd_ring.c           |  202 +++++++++++++-----------------------
 lib/librte_pmd_ring/rte_eth_ring.c |    3 +-
 2 files changed, 73 insertions(+), 132 deletions(-)

             reply	other threads:[~2014-07-09 14:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 14:35 Pablo de Lara [this message]
2014-07-09 14:35 ` [dpdk-dev] [PATCH 1/2] ring_pmd: Removed extra devices creation when passing vdev parameter Pablo de Lara
2014-07-09 14:35 ` [dpdk-dev] [PATCH 2/2] app/test: Simplified ring pmd test Pablo de Lara
2014-07-09 15:20 ` [dpdk-dev] [PATCH 0/2] Fixed/Simplified Ring PMD Neil Horman
2014-07-09 20:07   ` [dpdk-dev] PMD for Cisco VIC Ethernet NIC - Request for guidelines for submission Hobywan Kenoby
2014-07-11  7:46     ` Sujith Sankar (ssujith)
2014-07-11 13:16       ` Hobywan Kenoby
2014-07-21  3:39         ` Sujith Sankar (ssujith)
2014-07-22 14:54   ` [dpdk-dev] [PATCH 0/2] Fixed/Simplified Ring PMD Thomas Monjalon

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=1404916536-1364-1-git-send-email-pablo.de.lara.guarch@intel.com \
    --to=pablo.de.lara.guarch@intel.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).