Because after enqueueing, the buffers are dropped with error “successfully 
enqueued”. Check “sh error”. 

Florin

> On Mar 17, 2018, at 1:03 AM, Shashi Kant Singh <sksi...@altiostar.com> wrote:
> 
> Hi
>
> I changed the vcl_test_server / client from TCP to UDP.
>
> Question: Why does the UDP enqueued marked as error_drop?
>
>
>
> I get the following in my setup:
>
>
> how interface
>               Name               Idx       State          Counter          
> Count
> GigabitEthernet0/7/0              1         up       rx packets               
>       6
>                                                      rx bytes                 
>     488
>                                                      tx packets               
>       6
>                                                      tx bytes                 
>     472
>                                                      drops                    
>       6
>                                                      ip4                      
>       6
> GigabitEthernet0/8/0              2         up       
> local0                            0        down     
> vpp# vpp# show interface
>
> SERVER:
> [root@vbbubng6-shashi-2 vpp]# 
> ./build-root/build-vpp-native/vpp/vcl_test_server 5682
>
> SERVER: Waiting for a client to connect on port 5682...
> SERVER: Got a connection -- fd = 2 (0x00000002)!
> SERVER: Got a connection -- fd = 3 (0x00000003)!
> SERVER (fd 3): RX (14 bytes) - '12345'
> SERVER (fd 3): TX (6 bytes) - '12345'
> SERVER (fd 3): RX (14 bytes) - '12345'
> SERVER (fd 3): TX (6 bytes) - '12345'
>
> epoll_wait() timeout!
>
>
> CLIENT:
> ------------
> Type some characters and hit <return>
> ('#H' for help): 12345
>
> CLIENT: Received  52 ffffffce, fffffffa , ffffffed , fffffffe 1 0, 0 , 0 , 
> ffffffff ffffffff ffffffff, ffffffff , 
> CLIENT (fd 4): TX (6 bytes) - '12345'
> CLIENT (fd 4): RX (6 bytes) - '12345'
>
> Type some characters and hit <return>
> ('#H' for help):
>
>
> Packet 3
>
> 16:04:08:600447: dpdk-input
>   GigabitEthernet0/7/0 rx queue 0
>   buffer 0x2eef: current data 14, length 80, free-list 0, clone-count 0, 
> totlen-nifb 0, trace 0x2
>                  l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 
> l3-hdr-offset 14
>   PKT MBUF: port 0, nb_segs 1, pkt_len 94
>     buf_len 2176, data_len 94, ol_flags 0x0, data_off 128, phys_addr 
> 0x266bbc40
>     packet_type 0x0 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
>   IP4: fa:16:3e:59:76:83 -> fa:16:3e:1c:60:fe
>   UDP: 192.168.210.30 -> 192.168.220.30
>     tos 0x00, ttl 64, length 80, checksum 0xc703
>     fragment id 0x440b, flags DONT_FRAGMENT
>   UDP: 50016 -> 5682
>     length 60, checksum 0xd9f8
> 16:04:08:600460: ip4-input
>   UDP: 192.168.210.30 -> 192.168.220.30
>     tos 0x00, ttl 64, length 80, checksum 0xc703
>     fragment id 0x440b, flags DONT_FRAGMENT
>   UDP: 50016 -> 5682
>     length 60, checksum 0xd9f8
> 16:04:08:600469: ip4-lookup
>   fib 0 dpo-idx 6 flow hash: 0x00000000
>   UDP: 192.168.210.30 -> 192.168.220.30
>     tos 0x00, ttl 64, length 80, checksum 0xc703
>     fragment id 0x440b, flags DONT_FRAGMENT
>   UDP: 50016 -> 5682
>     length 60, checksum 0xd9f8
> 16:04:08:600472: ip4-local
>     UDP: 192.168.210.30 -> 192.168.220.30
>       tos 0x00, ttl 64, length 80, checksum 0xc703
>       fragment id 0x440b, flags DONT_FRAGMENT
>     UDP: 50016 -> 5682
>       length 60, checksum 0xd9f8
> 16:04:08:600475: ip4-udp-lookup
>   UDP: src-port 50016 dst-port 5682
> 16:04:08:600477: udp4-input
>   UDP_INPUT: connection 3, disposition 4, thread 2
> 16:04:08:600484: error-drop
>   udp4-input: UDP packets enqueued
>
>
>
> 

Reply via email to