[vpp-dev] Flowprobe/IPFIX export

2019-01-24 Thread Harish Patil
Hi, Need few clarifications on IPFIX support in the latest VPP. I went thru' codebase of older releases and understand how IPFIX support has evolved from 16.09 thru' the latest, in terms of enhancements and refactoring from vnet/vnet/flow,classify to flowperpkt plugin and now as flowprobe plugin.

Re: [vpp-dev] VNET classifier table/session

2019-01-18 Thread Harish Patil
FlowProbe plugin which implements some of the information entities. Pls let me know. Thanks, Harish On Tue, Jan 15, 2019 at 9:45 AM Harish Patil wrote: > Hi Andrew, > Thanks much for the pointers. > Shall go thru' them and revert back if I have further questions. > Thanks, > >

Re: [vpp-dev] VNET classifier table/session

2019-01-15 Thread Harish Patil
ier with IPFIX: > > https://www.mail-archive.com/vpp-dev@lists.fd.io/msg01820.html > > --a > > On 15 Jan 2019, at 08:11, Harish Patil wrote: > > Hi, > > Can you please provide few examples (with right syntax and little > explanation) on to how to use VNET c

[vpp-dev] VNET classifier table/session

2019-01-14 Thread Harish Patil
Hi, Can you please provide few examples (with right syntax and little explanation) on to how to use VNET classify table and classify session in relatively older VPP releases. "classify table [miss-next|l2-miss_next|acl-miss-next ]" "\n mask buckets [skip ] [match ] [del]", "classify

Re: [vpp-dev] Heap allocation

2018-12-05 Thread Harish Patil
hat clib_mem_alloc() and variants mean “allocate memory from the > current per-thread heap,” which is easily changed for a moment as shown > above. > > > > Please read through src/vppinfra/{mem.h, dlmalloc.[ch]} carefully and > understand what’s going on before you jump in. > >

[vpp-dev] Heap allocation

2018-12-05 Thread Harish Patil
Hi, I would like to pre-allocate separate heap space (outside of main heap) and be able to use the returned memory for my application's memory needs (just like malloc()). It seems we can have up to 256 heaps. Have few questions around this: 1) My understanding is that currently the main heap is

Re: [vpp-dev] Container Communication

2018-06-25 Thread Harish Patil
memif interface could be one other option. Thanks, Harish On Mon, Jun 25, 2018 at 11:55 AM, .ılı.D'p@k.ılı. wrote: > Hi Guys, > > I have a 3rd party app running as a container and i have vpp instance > running as another container. > What is the best way for packets to be sent over from vpp

Re: [vpp-dev] SPAN feature backport

2018-06-15 Thread Harish Patil
AM, Damjan Marion wrote: > > That's pretty bad idea. Beside feature arcs, SPAN is also using buffer > cloning which is introduced post 16.06. > > 16.06 is very old release, not maintained, strongly suggest to move to new > version... > > > On 15 Jun 2018, at 17:07,

[vpp-dev] SPAN feature backport

2018-06-15 Thread Harish Patil
Hi, I are currently using VPP 16.06 release. We would like to enable SPAN feature (port mirroring) in 16.06, but it is available only in VPP 17.01 release and above. It seems SPAN module depends on vnet feature arc (vnet/feature/). So my question is can we bypass vnet feature arc using some

Re: [vpp-dev] gdb break point of plugin not hit

2018-05-29 Thread Harish Patil
t Name Idx State Counter Count local00down DBGvpp# So I still have issues. Thanks, Harish On Tue, May 29, 2018 at 11:13 AM, Harish Patil wrote: > Hi Damjan, > Thanks. > > Yes I do see show run hitting the

Re: [vpp-dev] gdb break point of plugin not hit

2018-05-29 Thread Harish Patil
> Damjan > > On 25 May 2018, at 21:12, Harish Patil wrote: > > Hi, > > I built VPP using make -j build TAG=vpp_debug with export > SAMPLE_PLUGIN=yes; The VPP release is origin/stable/1710. First I verified > that sample_plugin.so is loaded. > > [root@local

[vpp-dev] gdb break point of plugin not hit

2018-05-25 Thread Harish Patil
Hi, I built VPP using make -j build TAG=vpp_debug with export SAMPLE_PLUGIN=yes; The VPP release is origin/stable/1710. First I verified that sample_plugin.so is loaded. [root@localhost vpp]# make run .. load_one_plugin:184: Loaded plugin: pppoe_plugin.so (PPPoE) load_one_plugin:184: Loaded