Re: [vpp-dev] Weird VPP API message processing failure

On Wed, Jan 18, 2017 at 12:24 PM, Damjan Marion wrote: > > I see. > > But how come vat doesn't do this [msg ID mapping] step? > > Likely somebody needs to do the work… > > Thanks, > Damjan > Ed, As I indicated when we spoke, I have implemented the gunky details of establishing the mapping from

Re: [vpp-dev] Weird VPP API message processing failure

> On 18 Jan 2017, at 17:14, Jon Loeliger wrote: > > On Wed, Jan 18, 2017 at 5:55 AM, Damjan Marion > wrote: > > -DDPDK=1 will disappear soon when dpdk becomes a plugin… > > Thanks, > Damjan > > Damjan, > > Will the DPDK that VPP builds be packaged and made av

Re: [vpp-dev] Weird VPP API message processing failure

> On 18 Jan 2017, at 16:28, Jon Loeliger wrote: > > > > On Wed, Jan 18, 2017 at 5:55 AM, Damjan Marion > wrote: > As Ole explained, please use vl_api_get_msg_index. > > -DDPDK=1 will disappear soon when dpdk becomes a plugin… > > Thanks, > > Damjan > > I se

Re: [vpp-dev] Weird VPP API message processing failure

On Wed, Jan 18, 2017 at 5:55 AM, Damjan Marion wrote: > > -DDPDK=1 will disappear soon when dpdk becomes a plugin… > > Thanks, > Damjan > Damjan, Will the DPDK that VPP builds be packaged and made available from the "make pkg-{rpm,deb}" targets? I see references to DPDK in the vpp.spec file, a

Re: [vpp-dev] Weird VPP API message processing failure

On Wed, Jan 18, 2017 at 5:55 AM, Damjan Marion wrote: > As Ole explained, please use vl_api_get_msg_index. > > -DDPDK=1 will disappear soon when dpdk becomes a plugin… > > Thanks, > > Damjan > I see. But how come vat doesn't do this step? jdl ___ vpp

Re: [vpp-dev] Weird VPP API message processing failure

> On 17 Jan 2017, at 22:53, Jon Loeliger wrote: > > > On Tue, Jan 17, 2017 at 3:45 PM, Alexander Popovsky (apopovsk) > mailto:apopo...@cisco.com>> wrote: > We have seen a similar issue related to the same ‘API refactoring : dpdk’ > change. > We are using an external API binding layer in C-lan

Re: [vpp-dev] Weird VPP API message processing failure

On Tue, Jan 17, 2017 at 3:45 PM, Alexander Popovsky (apopovsk) < apopo...@cisco.com> wrote: > We have seen a similar issue related to the same ‘API refactoring : dpdk’ > change. > We are using an external API binding layer in C-language in our VPP based > solution. > After the change, it took some

Re: [vpp-dev] Weird VPP API message processing failure

message id to name mapping is now part of the API itself. See commit 557d128b Use the u32 vl_api_get_msg_index (u8 * name_and_crc) API. Or do it via the pneum library. O. > > Thanks, > -AI > > From: on behalf of Jon Loeliger > > Date: Tuesday, January 17, 2017 at 11:12 AM

Re: [vpp-dev] Weird VPP API message processing failure

, January 17, 2017 at 11:12 AM To: vpp-dev Subject: Re: [vpp-dev] Weird VPP API message processing failure On Mon, Jan 16, 2017 at 6:33 PM, Jon Loeliger wrote: Folks, We are seeing a really strange VPP API message processing problem. The scenario goes like this... I've started to isolate it

Re: [vpp-dev] Weird VPP API message processing failure

On Mon, Jan 16, 2017 at 6:33 PM, Jon Loeliger wrote: > Folks, > > We are seeing a really strange VPP API message processing problem. > The scenario goes like this... > > > I've started to isolate it with git bisect, and so far I believe the > behavior changed between these commits: > > $ git log

Re: [vpp-dev] Weird VPP API message processing failure

Hi Jon, > We are seeing a really strange VPP API message processing problem. > The scenario goes like this... > > Our CLI issues C API calls through the vlib API. The messages hit > the shared memory queue, but are not processed. They sit there. Is it VPP that does not process the messages or

[vpp-dev] Weird VPP API message processing failure

Folks, We are seeing a really strange VPP API message processing problem. The scenario goes like this... Our CLI issues C API calls through the vlib API. The messages hit the shared memory queue, but are not processed. They sit there. Later, we fire up, say, vppctl and do a "show api" command.