Hello all,

I am good with having a call on Friday early AM PST.

Just a quick note on additional functionality tests:

- It makes sense to test with regular Linux forwarder (e.g. bridge), or even 
Windows. Not for performances, but for virtio drivers compatibility.
I would even suggest that we try this with IMIX instead of just 64bits (Drivers 
may have surprising behaviours with different packet sizes).

- Test reconnect.
This is pretty challenging as it depends on many factors (qemu version, 
server/client mode, VM driver... ).
But I think we have a few cases where reconnect actually works (others do not 
work well and that is most of the time not due to VPP).
It would be good to make sure that some patch does not break those few cases 
where is works.

- Pierre

Le 30 nov. 2016 à 03:27, Maciek Konstantynowicz (mkonstan) 
<mkons...@cisco.com<mailto:mkons...@cisco.com>> a écrit :


Here is the first draft:

I did my best to capture all inputs as per this thread. But it’s hardly 
readable yet - requires more TLC :)
See what you think - feel free to add/edit things directly on 
FD.io<http://fd.io/> wiki page.

Suggest to discuss next steps on csit weekly call tomorrow, details here:


On 28 Nov 2016, at 07:37, Thomas F Herbert 
<therb...@redhat.com<mailto:therb...@redhat.com>> wrote:


At last week's CSIT meeting, Maciek 
(mkons...@cisco.com<mailto:mkons...@cisco.com>) offered to compile a summary 
suggestions on this mailing list.

On 11/22/2016 11:34 AM, Pierre Pfister (ppfister) wrote:
Hello Thomas,

Sorry I haven't reached out faster, I was travelling.

Please have a look at vppsb/vhost-test
It includes a standalone script which provides VPP and VM configuration for PVP 
- Runs testpmd in the VM
- Supports various CPU configuration for VPP
- Can run with or without gdb, debug or release

Not committed yet:
- Supports VM restart
- Support for VPP restart
- Support for multiple additional (dead) vhost interface

I did that outside of the context of CSIT so people can:
- Look at it and see what are the optimisations that are used
- Use it without CSIT

I will keep using and improving it because I use it for my own development and 
testing purposes.

Rest of this inline.

Le 8 nov. 2016 à 22:25, Thomas F Herbert 
<<mailto:therb...@redhat.com>therb...@redhat.com<mailto:therb...@redhat.com>> a 
écrit :


Soliciting opinions from people as to vhost-user testing scenarios and guest 
modes in fd.io<http://fd.io/> CSIT testing of VPP - vhost-user.

I will forward to this mailing list as well as summarize any additional 

I asked some people that happen to be here at OVSCON as well as some Red Hat 
and Intel people. I am also including some people that are involved in upstream 
vhost-user work in DPDK.

So far, I have the following feedback with an attempt to condense feedback and 
to keep the list small. If I left out anything, let me know.

In addition to the PVP tests done now with small packets.

Testpmd in guest is OK for now.

1 Add multiple VMs (How many?)

Makes sense to me. 2 is enough (4 would be good number).

2 Both multi-queue and single-queue

Yes. Ideally, 1-2-4 queues.
With different number of workers (0 workers, i.e. single VPP thread, 1 worker, 
queues*2 workers).

3 Tests that cause the equivalent of multiple flows in OVS. Varying variety of 
traffic including layer 2 and layer 3 traffic.

Yes. Should test with L2 and L3.

4 Multiple IF's (Guest or Host or Both?)

But more importantly, I think, we need to have VM restart and interface restart 
(delete - create).
OpenStack integration generates a significant amount of delete-recreate of 
vhost interface.

The following might not be doable by 17.01 and if not consider the following as 
a wish list for future:

1 vxLan tunneled traffic

2 VPP in guest with layer 2 and layer 3 vRouted traffic.

3 Additional Overlay/Underlay: MPLS

Thomas F Herbert
SDN Group
Office of Technology
Red Hat
vpp-dev mailing list

Thomas F Herbert
SDN Group
Office of Technology
Red Hat

vpp-dev mailing list

Reply via email to