From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Nicolás Pernas Maradei" <nicolas.pernas.maradei@emutex.com>,
"John McNamara" <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/3] pcap pmd improvements
Date: Tue, 28 Apr 2015 12:09:46 +0200 [thread overview]
Message-ID: <1913554.gDjadJrHcM@xps13> (raw)
In-Reply-To: <1425044560-23397-1-git-send-email-tero.aho@coriant.com>
Please Nicolas, John,
could we have a review of these patches?
Thanks
2015-02-27 15:42, Tero Aho:
> We have found it convenient to use pcap interfaces in early development
> when speed does not matter. However, pcap interfaces use fixed values
> for some properties like link status which makes it hard to simulate
> certain conditions.
>
> Here's series of small improvements we have originally used on top
> of v1.7.0 (now rebased to current master).
>
> Tero Aho (3):
> pcap: utilize underlying real interface properties
> pcap: add support for jumbo frames
> pcap: add byte and error counters into statistics
>
> lib/librte_pmd_pcap/rte_eth_pcap.c | 176 +++++++++++++++++++++++++++++++------
> 1 file changed, 151 insertions(+), 25 deletions(-)
next prev parent reply other threads:[~2015-04-28 10:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 13:42 Tero Aho
2015-02-27 13:42 ` [dpdk-dev] [PATCH 1/3] pcap: utilize underlying real interface properties Tero Aho
2015-04-28 13:49 ` Mcnamara, John
2015-02-27 13:42 ` [dpdk-dev] [PATCH 2/3] pcap: add support for jumbo frames Tero Aho
2015-04-28 13:52 ` Mcnamara, John
2015-06-10 9:08 ` [dpdk-dev] [dpdk-dev,2/3] " Maxim Uvarov
2015-06-10 9:43 ` Mcnamara, John
2015-02-27 13:42 ` [dpdk-dev] [PATCH 3/3] pcap: add byte and error counters into statistics Tero Aho
2015-04-28 14:00 ` Mcnamara, John
2015-02-27 13:50 ` [dpdk-dev] [PATCH 0/3] pcap pmd improvements Thomas Monjalon
2015-04-28 10:09 ` Thomas Monjalon [this message]
2015-04-28 12:09 ` Mcnamara, John
2015-04-29 8:29 ` Nicolas Pernas Maradei
2015-04-28 12:27 ` Mcnamara, John
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=1913554.gDjadJrHcM@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=nicolas.pernas.maradei@emutex.com \
/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).