From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Paul Atkins <patkins@brocade.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/3] null driver improvements for testability
Date: Fri, 29 Jan 2016 17:31:02 +0100 [thread overview]
Message-ID: <1600067.TyQ2MXbqf2@xps13> (raw)
In-Reply-To: <1454084293-5722-1-git-send-email-patkins@brocade.com>
Hi Paul,
2016-01-29 16:18, Paul Atkins:
> This patchset adds functionality to the null driver help when testing
> a dataplane that uses dpdk. The idea is that the the dataplane can
> have multiple null interfaces attached, and each of theses can be
> assigned a mac address. Packets can then be injected into the null
> drivers by adding them to a ring, giving the application complete
> control of the packets that arrive. Packets that are sent by a null
> driver can be stored on a ring, where the application can pick them up
> and verify it is what was expected. To allow the application to know
> when packets have been pulled of the rx ring, counters of the number of
> times an rx poll has been made are kept, and these can be retrieved via
> the existing APIs.
I have not read your code, just read this description.
It sounds like being a ring PMD. Have you already checked it?
http://dpdk.org/browse/dpdk/tree/drivers/net/ring/rte_eth_ring.c
next prev parent reply other threads:[~2016-01-29 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 16:18 Paul Atkins
2016-01-29 16:18 ` [dpdk-dev] [PATCH 1/3] null: add a new arg to allow users to specify ether address Paul Atkins
2016-01-29 16:18 ` [dpdk-dev] [PATCH 2/3] null: add rings to allow user to provide the mbufs for rx/tx Paul Atkins
2016-01-29 16:18 ` [dpdk-dev] [PATCH 3/3] null: add xstats to provide the number of rx polls Paul Atkins
2016-01-29 16:31 ` Thomas Monjalon [this message]
2016-01-29 16:47 ` [dpdk-dev] [PATCH 0/3] null driver improvements for testability Paul Atkins
2016-02-17 17:23 ` Bruce Richardson
2016-02-18 12:19 ` Paul Atkins
2016-02-23 15:21 ` Bruce Richardson
2016-02-23 15:24 ` Paul Atkins
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=1600067.TyQ2MXbqf2@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=patkins@brocade.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).