From: mukawa@igel.co.jp
To: dev@dpdk.org
Cc: nakajima.yoshihiro@lab.ntt.co.jp, masutani.hitoshi@lab.ntt.co.jp
Subject: [dpdk-dev] [PATCH 0/2] PMD for performance measurement
Date: Tue, 30 Sep 2014 18:56:08 +0900 [thread overview]
Message-ID: <1412070970-5625-1-git-send-email-mukawa@igel.co.jp> (raw)
In-Reply-To: <mukawa@igel.co.jp>
From: Tetsuya Mukawa <mukawa@igel.co.jp>
Hi,
Here are patches to add the new PMD like '/dev/null'.
This PMD is a driver for virtual device. When an application call rx,
it just allocates mbufs and returns those. Also tx, it just frees mbufs.
Main purpose of the PMD is measuring rough throughputs of a VDEV PMD.
To measure rough throughputs between PMD1 and PMD2, prepare following
environment.
+-------------------------------+
| testpmd1 |
+-------------+------+----------+
| Target PMD1 | | null PMD |
+---++--------+ +----------+
||
|| Target path
||
+---++--------+ +----------+
| Target PMD2 | | null PMD |
+-------------+------+----------+
| testpmd2 |
+-------------------------------+
changes from RFC:
* change the copyright of this PMD.
* change commit logs.
Tetsuya Mukawa (2):
librte_pmd_null: Add null PMD
librte_pmd_null: Enable librte_pmd_null
config/common_bsdapp | 5 +
config/common_linuxapp | 5 +
lib/Makefile | 1 +
lib/librte_pmd_null/Makefile | 58 +++++
lib/librte_pmd_null/rte_eth_null.c | 474 +++++++++++++++++++++++++++++++++++++
mk/rte.app.mk | 4 +
6 files changed, 547 insertions(+)
create mode 100644 lib/librte_pmd_null/Makefile
create mode 100644 lib/librte_pmd_null/rte_eth_null.c
--
1.9.1
next reply other threads:[~2014-09-30 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 9:56 mukawa [this message]
2014-09-30 9:56 ` [dpdk-dev] [PATCH 1/2] librte_pmd_null: Add null PMD mukawa
2014-09-30 13:05 ` Thomas Monjalon
2014-10-01 1:41 ` Tetsuya Mukawa
2014-09-30 9:56 ` [dpdk-dev] [PATCH 2/2] librte_pmd_null: Enable librte_pmd_null mukawa
2014-09-30 11:23 ` Neil Horman
2014-10-01 1:39 ` Tetsuya Mukawa
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=1412070970-5625-1-git-send-email-mukawa@igel.co.jp \
--to=mukawa@igel.co.jp \
--cc=dev@dpdk.org \
--cc=masutani.hitoshi@lab.ntt.co.jp \
--cc=nakajima.yoshihiro@lab.ntt.co.jp \
/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).