<div dir="ltr">Tested-by: Joshua Washington <<a href="mailto:joshwash@google.com">joshwash@google.com</a>></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 31, 2023 at 2:05 AM Ferruh Yigit <<a href="mailto:ferruh.yigit@amd.com">ferruh.yigit@amd.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 1/31/2023 1:51 AM, Joshua Washington wrote:<br>
> Hello,<br>
> <br>
> I tested it out, and the updates to testpmd seem to work.<br>
> <br>
<br>
Hi Joshua,<br>
<br>
Thanks for testing, I will send a patch soon.<br>
<br>
But this was testpmd issue, do you have any objection with the net/gve<br>
patch, if not can you please record this with ack/review/tested-by tags,<br>
so I can proceed with it.<br>
<br>
> Before applying the second patch:<br>
> ---------------------- Forward statistics for port 0<br>
> ----------------------<br>
> RX-packets: 0 RX-dropped: 0 RX-total: 0<br>
> TX-packets: 43769238 TX-dropped: 62634 TX-total: 43831872<br>
> <br>
> ----------------------------------------------------------------------------<br>
> <br>
> ---------------------- Forward statistics for port 1<br>
> ----------------------<br>
> RX-packets: 0 RX-dropped: 0 RX-total: 0<br>
> TX-packets: 43761119 TX-dropped: 70753 TX-total: 43831872<br>
> <br>
> ----------------------------------------------------------------------------<br>
> <br>
> +++++++++++++++ Accumulated forward statistics for all<br>
> ports+++++++++++++++<br>
> RX-packets: 0 RX-dropped: 0 RX-total: 0<br>
> TX-packets: 87530357 TX-dropped: 157302 TX-total: 87687659<br>
> <br>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>
> <br>
> 62634 + 70753 = 133387 != 157302<br>
> <br>
> After applying the second patch:<br>
> ---------------------- Forward statistics for port 0<br>
> ----------------------<br>
> RX-packets: 0 RX-dropped: 0 RX-total: 0<br>
> TX-packets: 12590721 TX-dropped: 36638 TX-total: 12627359<br>
> <br>
> ----------------------------------------------------------------------------<br>
> <br>
> ---------------------- Forward statistics for port 1<br>
> ----------------------<br>
> RX-packets: 0 RX-dropped: 0 RX-total: 0<br>
> TX-packets: 12596255 TX-dropped: 31746 TX-total: 12628001<br>
> <br>
> ----------------------------------------------------------------------------<br>
> <br>
> +++++++++++++++ Accumulated forward statistics for all<br>
> ports+++++++++++++++<br>
> RX-packets: 0 RX-dropped: 0 RX-total: 0<br>
> TX-packets: 25186976 TX-dropped: 68384 TX-total: 25255360<br>
> <br>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>
> <br>
> Thanks,<br>
> Josh<br>
> <br>
> On Wed, Jan 18, 2023 at 8:22 AM Ferruh Yigit <<a href="mailto:ferruh.yigit@amd.com" target="_blank">ferruh.yigit@amd.com</a><br>
> <mailto:<a href="mailto:ferruh.yigit@amd.com" target="_blank">ferruh.yigit@amd.com</a>>> wrote:<br>
> <br>
> On 12/19/2022 7:38 PM, Joshua Washington wrote:<br>
> > Hello,<br>
> ><br>
> > As it turns out, this error actually propagates to the "total"<br>
> stats as<br>
> > well, which I assume is just calculated by adding TX-packets and<br>
> > TX-dropped. Here are the full stats from the example that Rushil<br>
> mentioned:<br>
> ><br>
> > ---------------------- Forward statistics for port 0<br>
> > ----------------------<br>
> > RX-packets: 2453802 RX-dropped: 0 RX-total:<br>
> 2453802<br>
> > TX-packets: 34266881 TX-dropped: 447034 TX-total:<br>
> 34713915<br>
> > <br>
> ><br>
> ----------------------------------------------------------------------------<br>
> ><br>
> > ---------------------- Forward statistics for port 1<br>
> > ----------------------<br>
> > RX-packets: 34713915 RX-dropped: 0 RX-total:<br>
> 34713915<br>
> > TX-packets: 2453802 TX-dropped: 0 TX-total:<br>
> 2453802<br>
> > <br>
> ><br>
> ----------------------------------------------------------------------------<br>
> ><br>
> > +++++++++++++++ Accumulated forward statistics for all<br>
> > ports+++++++++++++++<br>
> > RX-packets: 37167717 RX-dropped: 0 RX-total:<br>
> 37167717<br>
> > TX-packets: 36720683 TX-dropped: 807630 TX-total:<br>
> 37528313<br>
> > <br>
> ><br>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>
> ><br>
> > It can be seen that the stats for the individual ports are consistent,<br>
> > but the TX-total and TX-dropped are not consistent with the stats for<br>
> > the individual ports, as I believe that the TX-total and RX-total<br>
> > accumulated stats should be equal.<br>
> ><br>
> <br>
> Hi Joshua, Rushil,<br>
> <br>
> As I checked for it, issue may be related to testpmd stats display,<br>
> <br>
> While displaying per port TX-dropped value, it only takes<br>
> 'ports_stats[pt_id].tx_dropped' into account,<br>
> but for accumulated TX-dropped results it takes both<br>
> 'ports_stats[pt_id].tx_dropped' & 'stats.oerrors' into account.<br>
> <br>
> If you can reproduce it easily, can you please test with following<br>
> change:<br>
> <br>
> diff --git a/app/test-pmd/testpmd.c b/app/test-pmd/testpmd.c<br>
> index 134d79a55547..49322d07d7d6 100644<br>
> --- a/app/test-pmd/testpmd.c<br>
> +++ b/app/test-pmd/testpmd.c<br>
> @@ -2056,6 +2056,8 @@ fwd_stats_display(void)<br>
> fwd_cycles += fs->core_cycles;<br>
> }<br>
> for (i = 0; i < cur_fwd_config.nb_fwd_ports; i++) {<br>
> + uint64_t tx_dropped = 0;<br>
> +<br>
> pt_id = fwd_ports_ids[i];<br>
> port = &ports[pt_id];<br>
> <br>
> @@ -2077,8 +2079,9 @@ fwd_stats_display(void)<br>
> total_recv += stats.ipackets;<br>
> total_xmit += stats.opackets;<br>
> total_rx_dropped += stats.imissed;<br>
> - total_tx_dropped += ports_stats[pt_id].tx_dropped;<br>
> - total_tx_dropped += stats.oerrors;<br>
> + tx_dropped += ports_stats[pt_id].tx_dropped;<br>
> + tx_dropped += stats.oerrors;<br>
> + total_tx_dropped += tx_dropped;<br>
> total_rx_nombuf += stats.rx_nombuf;<br>
> <br>
> printf("\n %s Forward statistics for port %-2d %s\n",<br>
> @@ -2105,8 +2108,8 @@ fwd_stats_display(void)<br>
> <br>
> printf(" TX-packets: %-14"PRIu64" TX-dropped:<br>
> %-14"PRIu64<br>
> "TX-total: %-"PRIu64"\n",<br>
> - stats.opackets, ports_stats[pt_id].tx_dropped,<br>
> - stats.opackets + ports_stats[pt_id].tx_dropped);<br>
> + stats.opackets, tx_dropped,<br>
> + stats.opackets + tx_dropped);<br>
> <br>
> if (record_burst_stats) {<br>
> if (ports_stats[pt_id].rx_stream)<br>
> <br>
> <br>
> ><br>
> > On Mon, Dec 19, 2022 at 11:17 AM Rushil Gupta <<a href="mailto:rushilg@google.com" target="_blank">rushilg@google.com</a><br>
> <mailto:<a href="mailto:rushilg@google.com" target="_blank">rushilg@google.com</a>><br>
> > <mailto:<a href="mailto:rushilg@google.com" target="_blank">rushilg@google.com</a> <mailto:<a href="mailto:rushilg@google.com" target="_blank">rushilg@google.com</a>>>> wrote:<br>
> ><br>
> > Hi all<br>
> > Josh just found out some inconsistencies in the Tx/Rx<br>
> statistics sum<br>
> > for all ports. Not sure if we can screenshot here but it goes like<br>
> > this:<br>
> > Tx-dropped for port0: 447034<br>
> > Tx-dropped for port1: 0<br>
> > Accumulated forward statistics for all ports: 807630<br>
> ><br>
> > Please note that this issue is only with Tx-dropped (not<br>
> > Tx-packets/Tx-total).<br>
> ><br>
> ><br>
> > On Wed, Dec 7, 2022 at 8:39 AM Stephen Hemminger<br>
> > <<a href="mailto:stephen@networkplumber.org" target="_blank">stephen@networkplumber.org</a><br>
> <mailto:<a href="mailto:stephen@networkplumber.org" target="_blank">stephen@networkplumber.org</a>><br>
> <mailto:<a href="mailto:stephen@networkplumber.org" target="_blank">stephen@networkplumber.org</a><br>
> <mailto:<a href="mailto:stephen@networkplumber.org" target="_blank">stephen@networkplumber.org</a>>>> wrote:<br>
> > ><br>
> > > On Wed, 7 Dec 2022 15:09:08 +0000<br>
> > > Ferruh Yigit <<a href="mailto:ferruh.yigit@amd.com" target="_blank">ferruh.yigit@amd.com</a><br>
> <mailto:<a href="mailto:ferruh.yigit@amd.com" target="_blank">ferruh.yigit@amd.com</a>> <mailto:<a href="mailto:ferruh.yigit@amd.com" target="_blank">ferruh.yigit@amd.com</a><br>
> <mailto:<a href="mailto:ferruh.yigit@amd.com" target="_blank">ferruh.yigit@amd.com</a>>>><br>
> > wrote:<br>
> > ><br>
> > > > On 11/24/2022 7:33 AM, Junfeng Guo wrote:<br>
> > > > > Add support for dev_ops of stats_get and stats_reset.<br>
> > > > ><br>
> > > > > Queue stats update will be moved into xstat [1], but the<br>
> basic<br>
> > stats<br>
> > > > > items may still be required. So we just keep the remaining<br>
> > ones and<br>
> > > > > will implement the queue stats via xstats in the coming<br>
> release.<br>
> > > > ><br>
> > > > > [1]<br>
> > > > > <a href="https://elixir.bootlin.com/dpdk/v22.07/" rel="noreferrer" target="_blank">https://elixir.bootlin.com/dpdk/v22.07/</a><br>
> <<a href="https://elixir.bootlin.com/dpdk/v22.07/" rel="noreferrer" target="_blank">https://elixir.bootlin.com/dpdk/v22.07/</a>><br>
> > <<a href="https://elixir.bootlin.com/dpdk/v22.07/" rel="noreferrer" target="_blank">https://elixir.bootlin.com/dpdk/v22.07/</a><br>
> <<a href="https://elixir.bootlin.com/dpdk/v22.07/" rel="noreferrer" target="_blank">https://elixir.bootlin.com/dpdk/v22.07/</a>>> \<br>
> > > > > source/doc/guides/rel_notes/deprecation.rst#L118<br>
> > > > ><br>
> > > > > Signed-off-by: Xiaoyun Li <<a href="mailto:xiaoyun.li@intel.com" target="_blank">xiaoyun.li@intel.com</a><br>
> <mailto:<a href="mailto:xiaoyun.li@intel.com" target="_blank">xiaoyun.li@intel.com</a>><br>
> > <mailto:<a href="mailto:xiaoyun.li@intel.com" target="_blank">xiaoyun.li@intel.com</a> <mailto:<a href="mailto:xiaoyun.li@intel.com" target="_blank">xiaoyun.li@intel.com</a>>>><br>
> > > > > Signed-off-by: Junfeng Guo <<a href="mailto:junfeng.guo@intel.com" target="_blank">junfeng.guo@intel.com</a><br>
> <mailto:<a href="mailto:junfeng.guo@intel.com" target="_blank">junfeng.guo@intel.com</a>><br>
> > <mailto:<a href="mailto:junfeng.guo@intel.com" target="_blank">junfeng.guo@intel.com</a> <mailto:<a href="mailto:junfeng.guo@intel.com" target="_blank">junfeng.guo@intel.com</a>>>><br>
> > > ><br>
> > > > <...><br>
> > > ><br>
> > > > > +static int<br>
> > > > > +gve_dev_stats_get(struct rte_eth_dev *dev, struct<br>
> > rte_eth_stats *stats)<br>
> > > > > +{<br>
> > > > > + uint16_t i;<br>
> > > > > +<br>
> > > > > + for (i = 0; i < dev->data->nb_tx_queues; i++) {<br>
> > > > > + struct gve_tx_queue *txq =<br>
> dev->data->tx_queues[i];<br>
> > > > > + if (txq == NULL)<br>
> > > > > + continue;<br>
> > > > > +<br>
> > > > > + stats->opackets += txq->packets;<br>
> > > > > + stats->obytes += txq->bytes;<br>
> > > > > + stats->oerrors += txq->errors;<br>
> > > ><br>
> > > > Hi Junfeng, Qi, Jingjing, Beilei,<br>
> > > ><br>
> > > > Above logic looks wrong to me, did you test it?<br>
> > > ><br>
> > > > If the 'gve_dev_stats_get()' called multiple times (without<br>
> > stats reset<br>
> > > > in between), same values will be keep added to stats.<br>
> > > > Some hw based implementations does this, because reading<br>
> from stats<br>
> > > > registers automatically reset those registers but this<br>
> shouldn't<br>
> > be case<br>
> > > > for this driver.<br>
> > > ><br>
> > > > I expect it to be something like:<br>
> > > ><br>
> > > > local_stats = 0<br>
> > > > foreach queue<br>
> > > > local_stats += queue->stats<br>
> > > > stats = local_stats<br>
> > ><br>
> > > The zero of local_stats is unnecessary.<br>
> > > The only caller of the PMD stats_get is rte_ethdev_stats_get<br>
> > > and it zeros the stats structure before calling the PMD.<br>
> > ><br>
> > ><br>
> > > int<br>
> > > rte_eth_stats_get(uint16_t port_id, struct rte_eth_stats *stats)<br>
> > > {<br>
> > > struct rte_eth_dev *dev;<br>
> > ><br>
> > > RTE_ETH_VALID_PORTID_OR_ERR_RET(port_id, -ENODEV);<br>
> > > dev = &rte_eth_devices[port_id];<br>
> > ><br>
> > > memset(stats, 0, sizeof(*stats));<br>
> > > ...<br>
> > > stats->rx_nombuf = dev->data->rx_mbuf_alloc_failed;<br>
> > > return eth_err(port_id, (*dev->dev_ops->stats_get)(dev,<br>
> > stats));<br>
> > ><br>
> > > If any PMD has extra memset in their stats get that could be<br>
> removed.<br>
> ><br>
> ><br>
> ><br>
> > --<br>
> ><br>
> > Joshua Washington | Software Engineer | <a href="mailto:joshwash@google.com" target="_blank">joshwash@google.com</a><br>
> <mailto:<a href="mailto:joshwash@google.com" target="_blank">joshwash@google.com</a>><br>
> > <mailto:<a href="mailto:joshwash@google.com" target="_blank">joshwash@google.com</a> <mailto:<a href="mailto:joshwash@google.com" target="_blank">joshwash@google.com</a>>> | (414)<br>
> 366-4423 <tel:(414)%20366-4423><br>
> > <br>
> <br>
> <br>
> <br>
> -- <br>
> <br>
> Joshua Washington | Software Engineer | <a href="mailto:joshwash@google.com" target="_blank">joshwash@google.com</a><br>
> <mailto:<a href="mailto:joshwash@google.com" target="_blank">joshwash@google.com</a>> | <a href="tel:(414)%20366-4423" value="+14143664423" target="_blank">(414) 366-4423</a><br>
> <br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><br><div style="line-height:1.5em;padding-top:10px;margin-top:10px;color:rgb(85,85,85);font-family:sans-serif"><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(213,15,37);padding-top:2px;margin-top:2px">Joshua Washington |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(51,105,232);padding-top:2px;margin-top:2px"> Software Engineer |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(0,153,57);padding-top:2px;margin-top:2px"> <a href="mailto:joshwash@google.com" target="_blank">joshwash@google.com</a> |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(238,178,17);padding-top:2px;margin-top:2px"> (414) 366-4423</span></div><span style="color:rgb(0,0,0);font-family:Tinos;font-size:medium"> </span><br></div></div>