DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/4] eth_ring: perf test and usability	improvements
Date: Tue, 03 Nov 2015 02:02:44 +0100	[thread overview]
Message-ID: <2068953.0G2UelKtxd@xps13> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8973C840E41@IRSMSX108.ger.corp.intel.com>

> > This patchset makes it easier to create ring pmd instances from code, by
> > providing a simple ring->ethdev wrapper function and also ensuring that
> > any created rings are ready for use immediately, without having to call
> > configure and rx/tx queue setup.
> > 
> > This set also contains a set of unit tests to compare the performance of
> > basic ring operations against the same operations via the ring ethdev.
> > This shows how the perf penalty can be significant for small bursts, but
> > is much less so for larger bursts of 32 packets.
> > 
> > Bruce Richardson (4):
> >   ring: enhance rte_eth_from_rings
> >   rte_ring: store memzone pointer inside ring
> >   ring: add rte_eth_from_ring function
> >   test: Add perf test for ring pmd
> 
> Series-acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>

Applied, thanks

      reply	other threads:[~2015-11-03  1:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 12:12 Bruce Richardson
2015-09-30 12:12 ` [dpdk-dev] [PATCH 1/4] ring: enhance rte_eth_from_rings Bruce Richardson
2015-09-30 12:12 ` [dpdk-dev] [PATCH 2/4] rte_ring: store memzone pointer inside ring Bruce Richardson
2015-10-13 14:29   ` Olivier MATZ
2015-09-30 12:12 ` [dpdk-dev] [PATCH 3/4] ring: add rte_eth_from_ring function Bruce Richardson
2015-09-30 12:12 ` [dpdk-dev] [PATCH 4/4] test: Add perf test for ring pmd Bruce Richardson
2015-10-30 13:53 ` [dpdk-dev] [PATCH 0/4] eth_ring: perf test and usability improvements De Lara Guarch, Pablo
2015-11-03  1:02   ` Thomas Monjalon [this message]

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=2068953.0G2UelKtxd@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=bruce.richardson@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).