From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bhavesh Davda <bhavesh@vmware.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] examples: new txburst application
Date: Fri, 30 Jan 2015 11:33:58 +0100 [thread overview]
Message-ID: <25405198.KkrSSHtStQ@xps13> (raw)
In-Reply-To: <1416335575-30717-1-git-send-email-bhavesh@vmware.com>
Hi Bhavesh,
2014-11-18 10:32, Bhavesh Davda:
> Test application to transmit 32-packet bursts of 220-byte UDP packets every
> 50 us, approximating 240,000 pps. We found it useful for testing hypervisor
> performance for a transmit-heavy but bursty workload in a VM with DPDK.
>
> Signed-off-by: Bhavesh Davda <bhavesh@vmware.com>
There was no review of your patch.
Maybe you should explain why you think it should be integrated as an example.
What is new compared to other examples?
Thanks
--
Thomas
next prev parent reply other threads:[~2015-01-30 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 18:32 Bhavesh Davda
2015-01-30 10:33 ` Thomas Monjalon [this message]
2015-01-30 16:29 ` Bhavesh Davda
2015-01-30 16:43 ` Thomas Monjalon
2015-01-30 16:48 ` Bhavesh Davda
2015-01-30 19:45 ` Wiles, Keith
2015-01-31 23:47 ` Wiles, Keith
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=25405198.KkrSSHtStQ@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bhavesh@vmware.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).