Re: [vpp-dev] sh hardware-interfaces extended stats are not showing up

AFAIK it is fixed, please try latest master and report back if it doesn't work. > On 20 Sep 2019, at 19:53, Devis Reagan wrote: > > Hi David , > > Is there any fix or work around for this extended stats issue > > Thanks > > On Thu, Aug 29, 2019 at 6:58 AM Carlito Nueno

Re: [vpp-dev] sh hardware-interfaces extended stats are not showing up

Hi David , Is there any fix or work around for this extended stats issue Thanks On Thu, Aug 29, 2019 at 6:58 AM Carlito Nueno wrote: > Hi David, > > I tried "vppctl interface collect detailed-stats enable" but it doesn't > work. > > I will git bisect as Damjan mentioned and try to see what cha

Re: [vpp-dev] [csit-dev] API check failure

I rebased one of my failing patches, and the API crc check passed. Thanks for your help! Dave 08:54:51 +++ export PYTHONPATH=/w/workspace/vpp-csit-verify-api-crc-master/csit 08:54:51 +++ PYTHONPATH=/w/workspace/vpp-csit-verify-api-crc-master/csit 08:54:51 +++ make json-api-files 08:54:51 /w/wor

Re: [vpp-dev] About VPP trace，why I trace add ip4_lookup, but when i show ,it does't have any record?

One can call vlib_trace_buffer(...) anywhere, but doing so on a packet which is already traced - from one of the input nodes - has a peculiar "fork" effect which may prove confusing. As Chris wrote: [we hope that] all device input nodes are capable of calling vlib_trace_buffer. Few if any inter

Re: [vpp-dev] [csit-dev] API check failure

Fixed. Short report: https://lists.fd.io/g/vpp-api-dev/message/34 Longer discussion on how to prevent similar things from happening in future: #csit-dev channel on FD.io slack. We will update the flag day document when we conclude the discussion. Vratko. -Original Message- From: Dave Bara

Re: [vpp-dev] HQOS shape questions #vpp_qos #vpp

May be packet fields (traffic from TRex) associated with pipe, tc, and queues are not randomized, so traffic is only going to specific scheduler queues. Please refer documentation to know offsets of packet fields. From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of hui12...@16

Re: [vpp-dev] [csit-dev] API check failure

Yes. Since folks have been unable to debug the problem so far, we need to disable voting on the API CRC checker job. Ed Kern [or anyone with appropriate access rights!]: please do that immediately, and send email to vpp-dev@lists.fd.io so folks can "recheck" patches which failed for no good reaso

[vpp-dev] CRC job reliable again

Yesterday, we did a risky thing of merging two [0] VPP [1] changes affecting APIs. Without verifying CSIT really is ready for the end result. Fixed [2] only now. From the process point of view, we have some possible improvements planned, but until we are able to implement them, we will be stickin

Re: [vpp-dev] About VPP trace，why I trace add ip4_lookup, but when i show ,it does't have any record?

Only input nodes are capable of starting a trace on a packet. Thanks, Chris. > On Sep 20, 2019, at 4:55 AM, wei_sky2...@163.com wrote: > > I use commond "trace add ip4_lookup 10" in vppctl. > when I show trace,no packets is recorded, why? > And I use trace add dpdk_input 10 , some packets can be

[vpp-dev] About VPP trace，why I trace add ip4_lookup, but when i show ,it does't have any record?

I use commond "trace add ip4_lookup 10" in vppctl. when I show trace,no packets is recorded, why? And I use trace add dpdk_input 10 , some packets can be recorded. Thanks! -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14028): https://lists.fd.io/g/

Re: [vpp-dev] hi guys, does any CLI support to filter out some pakcets with specific TCP port on physical interface ? thanks for any input

Thanks chemmin for your help. I see that classify table can provide support for l2 and l3, I wonder if the similar command provides support for TCP port filtering? Does anybody know that? Thanks Zhiyong From: Sun, Chenmin Sent: Friday, September 20, 2019 12:45 PM To: Yang, Zhiyong ; vpp-dev@lis