Hi
I have a setup with Intel 82576NS.
Port 0 is connected to internal network and is managed by igb driver
Port 1 is connected directly to PC which will serve as traffic generator.
When Port 1 is managed by igb driver eth interface is configured and I am
able to connect to traffic generator PC.
It is often useful to build with debug enabled, we add a config
(CONFIG_RTE_TOOLCHAIN_DEBUG) to do so.
Note: This patch does not include corresponding changes for ICC. The author
pleads abject ignorance in this regard, and welcomes recommendations. :-)
Signed-off-by: Cyril Chemparathy
---
conf
This commit adds a multi-flow traffic generator forwarding engine. In effect,
this forwarding mode functions very similar to the txonly mode, with the
difference that it generates multiple L4 flows.
Signed-off-by: Cyril Chemparathy
---
app/test-pmd/Makefile | 1 +
app/test-pmd/flowgen.c | 24
This commit adds a new forwarding mode, in which the source and destination
MAC addresses of packets are swapped before forwarding according to the
port-topology in effect. This has been designed for operation primarily with
--port-topology=loopback.
Signed-off-by: Cyril Chemparathy
---
app/tes
We allow a new --txpkts command-line parameter to configure segment sizes when
in txonly or flowgen forwarding modes.
Signed-off-by: Cyril Chemparathy
---
app/test-pmd/parameters.c | 57 +++
1 file changed, 57 insertions(+)
diff --git a/app/test-pmd/p
This commit allows testpmd forwarding mode selection through command line
parameters instead of having to set this up in interactive mode.
Signed-off-by: Cyril Chemparathy
---
app/test-pmd/parameters.c | 4
1 file changed, 4 insertions(+)
diff --git a/app/test-pmd/parameters.c b/app/test-p
This patch adds support for a command-line argument --auto-start (-a). When
running in interactive mode, this allows us to start traffic without user
intervention before dropping to the prompt.
Signed-off-by: Cyril Chemparathy
---
app/test-pmd/parameters.c | 20
app/test-pm
This commits adds a new "loop" option to the --port-topology argument. With
the loop option specified, ingress traffic is simply transmitted back on the
same interface.
Signed-off-by: Cyril Chemparathy
---
app/test-pmd/config.c | 16 ++--
app/test-pmd/parameters.c | 2 ++
app/t
Hi,
This patch series contains a few minor extensions to test-pmd. These changes
have been added primarily for convenience while testing out various scenarios
with DPDK.
Thanks
-- Cyril.
Cyril Chemparathy (6):
test-pmd: add support for single port loopback topology
test-pmd: add support for
From: Hiroshi Shimamoto
Same as PMD, there is a race condition between host and guest
in the guest MEMNIC kernel driver.
Guest PMD Host
Thread-A Thread-B vSwitch
|idx=0 |idx=0 |p[0] st!=2
|cmpxchg ||
|p[0] st->1 ||
|idx
From: Hiroshi Shimamoto
Because DPDK has its own compare and set function to optimize to
dedicated processor type, use that rte_atomic32_cmpset() instead of
cmpxchg macro which is specially introduced for MEMNIC.
Signed-off-by: Hiroshi Shimamoto
---
common/memnic.h | 12
pmd/pmd_
From: Hiroshi Shimamoto
The MEMNIC header file should be under Dual BSD/GPL license.
Put the license text "Dual BSD/GPL" into the file header.
Signed-off-by: Hiroshi Shimamoto
---
common/memnic.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/common/memnic.h b/common/memnic.h
index 8bd483
From: Hiroshi Shimamoto
There is a race condition, on transmit to host.
Guest PMD Host
Thread-A Thread-B vSwitch
|idx=0 |idx=0 |p[0] st!=2
|cmpxchg ||
|p[0] st->1 ||
|idx=1 ||
|fill data |
13 matches
Mail list logo