Re: [vpp-dev] vHost user test scenarios for CSIT - TWS meeting

REMINDER: Next call details: https://wiki.fd.io/view/TWS CSIT - vHost user test scenarios for CSIT Wednesday, 7 December 2016 09:00 | PST Time | 1 hr 17:00 | GMT Time (London, GMT) | 1 hr Join WebEx meeting: https://cisco.webex.com/ciscosales/j.php?MTID=m2d165f5c9f3fdf722826e7c05a4499c9 Mee

Re: [vpp-dev] vpp consistent per-packet latency

The prevailing vector size is a self-timed, stable equilibrium value, arranged by the graph dispatcher. Individual graph nodes don't have to worry about the problem. Follow the coding patterns you'll see all over the place, and you should be good. The graph dispatcher is essentially a while(1)

[vpp-dev] Reminder: vpp project 17.01 F0 (API freeze) tomorrow (12/7) at 5pm PST

Thanks... Dave ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] VPP -- Access-Lists

Hello VPP delevopers, I have a question regarding the deployment of access lists on a sub-interface or a physical interface to match on a certain IP. I have looked at the VPP WIKI Page and at www.docs.fd.io , however i cant find specific information. According to the out

[vpp-dev] vpp consistent per-packet latency

Based on VPP doc., the vector size (i.e. workload) for each node needs be adjusted dynamically for the consistent per-packet latency. Can someone point to me where are the codes or funcs. which change the vector size for consistent per-packet latency? When we implement a new node, do we need

Re: [vpp-dev] Vnet enum values in the python API

Hi Ole, On 06/12/2016, 10:25, "otr...@employees.org" wrote: >Neale, > >> What’s the best (i.e. least error prone) way to export enum values to the >> python API. >> >> For example; >> From l2/l2_vtr.h: >> >> /* VTR config options for API and CLI support */ >> typedef enum >> { >> … >> } l

Re: [vpp-dev] Vnet enum values in the python API

Neale, > What’s the best (i.e. least error prone) way to export enum values to the > python API. > > For example; > From l2/l2_vtr.h: > > /* VTR config options for API and CLI support */ > typedef enum > { > … > } l2_vtr_op_t; > > Is required for use in (from vpe.py) > > > def l2_interface