> On Thu, Apr 1, 2021 at 9:49 AM Lorenzo Bianconi <lorenzo@xxxxxxxxxx> wrote: > > > > > On Thu, Apr 1, 2021 at 1:57 AM Lorenzo Bianconi <lorenzo@xxxxxxxxxx> wrote: > > > > > > > > [...] > > > > > > - /* Inject into network stack */ > > > > - ret = netif_receive_skb_core(skb); > > > > - if (ret == NET_RX_DROP) > > > > - drops++; > > > > > > I guess we stop tracking "drops" with this patch? > > > > > > Thanks, > > > Song > > > > Hi Song, > > > > we do not report the packets dropped by the stack but we still count the drops > > in the cpumap. If you think they are really important I guess we can change > > return value of netif_receive_skb_list returning the dropped packets or > > similar. What do you think? > > I think we shouldn't silently change the behavior of the tracepoint below: > > trace_xdp_cpumap_kthread(rcpu->map_id, n, drops, sched, &stats); > > Returning dropped packets from netif_receive_skb_list() sounds good to me. Hi Song, I reviewed the netif_receive_skb_list() and I guess the code needed to count number of dropped frames is a bit intrusive and we need to add some checks in the hot path. Moreover the dropped frames are already accounted in the networking stack (e.g. mib counters for the ip traffic). Since drop counter is just exported in a tracepoint in cpu_map_kthread_run, I guess we can just not count dropped packets in the networking stack here and rely on the mib counters. What do you think? @Jesper: since you added the original code, what do you think about it? Regards, Lorenzo > > Thanks, > Song >
Attachment:
signature.asc
Description: PGP signature
