From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Cc: nakajima.yoshihiro@lab.ntt.co.jp, masutani.hitoshi@lab.ntt.co.jp
Subject: Re: [dpdk-dev] [PATCH v2] librte_pmd_null: Add null PMD
Date: Thu, 13 Nov 2014 13:17:55 +0100 [thread overview]
Message-ID: <5057307.FGrc0kAccs@xps13> (raw)
In-Reply-To: <1412139437-26749-2-git-send-email-mukawa@igel.co.jp>
Hi,
2014-10-01 13:57, mukawa@igel.co.jp:
> 'null PMD' is a driver of the virtual device particulary designed to measure
> performance of DPDK PMDs. When an application call rx, null PMD just allocates
> mbufs and returns those. Also tx, the PMD just frees mbufs.
>
> The PMD has following options.
> - size: specify packe size allocated by RX. Default packet size is 64.
> - copy: specify 1 or 0 to enable or disable copy while RX and TX.
> Default value is 0(disbaled).
> This option is used for emulating more realistic data transfer.
> Copy size is equal to packet size.
>
> To use the PMD, enable CONFIG_RTE_BUILD_SHARED_LIB in config file. Then
> compile the PMD as shared library. The library can be linked using '-d'
> option when an application invokes.
>
> Here is an example.
> $ sudo ./testpmd -c f -n 4 -d librte_pmd_null.so \
> --vdev 'eth_null0' --vdev 'eth_null1' -- -i
>
> If testpmd is compiled with CONFIG_RTE_BUILD_SHARED_LIB, it may need to
> specify more libraries using '-d' option.
>
> Signed-off-by: Tetsuya Mukawa <mukawa@igel.co.jp>
This patch is still pending because nobody reviewed it.
--
Thomas
next prev parent reply other threads:[~2014-11-13 12:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mukawa@igel.co.jp>
2014-10-01 4:57 ` [dpdk-dev] [PATCH v2] PMD for performance measurement mukawa
2014-10-01 4:57 ` [dpdk-dev] [PATCH v2] librte_pmd_null: Add null PMD mukawa
2014-11-13 12:17 ` Thomas Monjalon [this message]
2014-12-16 8:39 ` [dpdk-dev] [PATCH v3] " Tetsuya Mukawa
2014-12-16 8:44 ` Tetsuya Mukawa
2014-12-16 8:47 ` Thomas Monjalon
2014-12-16 8:49 ` Tetsuya Mukawa
2015-01-20 3:00 ` [dpdk-dev] [PATCH v4 1/2] " Tetsuya Mukawa
2015-01-20 3:00 ` [dpdk-dev] [PATCH v4 2/2] librte_pmd_null: Support port hotplug function Tetsuya Mukawa
2015-02-06 4:38 ` [dpdk-dev] [PATCH v6 1/2] librte_pmd_null: Add null PMD Tetsuya Mukawa
2015-02-06 4:38 ` [dpdk-dev] [PATCH v6 2/2] librte_pmd_null: Support port hotplug function Tetsuya Mukawa
2015-02-06 11:37 ` Iremonger, Bernard
2015-02-06 11:32 ` [dpdk-dev] [PATCH v6 1/2] librte_pmd_null: Add null PMD Iremonger, Bernard
2015-02-09 8:54 ` Tetsuya Mukawa
2015-02-12 2:44 ` [dpdk-dev] [PATCH v7 1/2] librte_pmd_null: Add Null PMD Tetsuya Mukawa
2015-02-12 2:44 ` [dpdk-dev] [PATCH v7 2/2] librte_pmd_null: Support port hotplug function Tetsuya Mukawa
2015-02-16 4:19 ` [dpdk-dev] [PATCH v8 1/2] librte_pmd_null: Add Null PMD Tetsuya Mukawa
2015-02-16 4:19 ` [dpdk-dev] [PATCH v8 2/2] librte_pmd_null: Support port hotplug function Tetsuya Mukawa
2015-02-16 16:38 ` Iremonger, Bernard
2015-02-16 16:38 ` [dpdk-dev] [PATCH v8 1/2] librte_pmd_null: Add Null PMD Iremonger, Bernard
2015-02-19 10:41 ` [dpdk-dev] [PATCH v9 " Tetsuya Mukawa
2015-02-19 10:41 ` [dpdk-dev] [PATCH v9 2/2] librte_pmd_null: Support port hotplug function Tetsuya Mukawa
2015-02-20 6:41 ` [dpdk-dev] [PATCH v10 1/2] librte_pmd_null: Add Null PMD Tetsuya Mukawa
2015-02-20 6:41 ` [dpdk-dev] [PATCH v10 2/2] librte_pmd_null: Support port hotplug function Tetsuya Mukawa
2015-02-23 5:12 ` [dpdk-dev] [PATCH v11 1/2] librte_pmd_null: Add Null PMD Tetsuya Mukawa
2015-02-23 5:12 ` [dpdk-dev] [PATCH v11 2/2] librte_pmd_null: Support port hotplug function Tetsuya Mukawa
2015-02-25 23:35 ` Thomas Monjalon
2015-02-26 0:49 ` Stephen Hemminger
2015-02-26 7:03 ` Thomas Monjalon
2015-02-26 9:06 ` Tetsuya Mukawa
2015-02-26 10:57 ` Thomas Monjalon
2015-02-26 11:50 ` Tetsuya Mukawa
2015-03-04 3:37 ` Tetsuya Mukawa
2015-02-26 12:21 ` Mcnamara, John
2015-02-26 15:36 ` Mcnamara, John
2015-02-27 1:31 ` Tetsuya Mukawa
2015-02-27 23:29 ` 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=5057307.FGrc0kAccs@xps13 \
--to=thomas.monjalon@6wind.com \
--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).