From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: RE: [TEST v10] ethdev: support single queue per port
Date: Thu, 7 Nov 2024 10:35:41 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F88D@smartserver.smartshare.dk> (raw)
In-Reply-To: <20241106152542.71d572e3@hermes.local>
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Thursday, 7 November 2024 00.26
T v10] ethdev: support single queue per port
>
> On Wed, 6 Nov 2024 22:02:16 +0000
> Morten Brørup <mb@smartsharesystems.com> wrote:
>
> > iff --git a/drivers/net/vmxnet3/vmxnet3_ethdev.c
> b/drivers/net/vmxnet3/vmxnet3_ethdev.c
> > index 78fac63ab6..1752c58069 100644
> > --- a/drivers/net/vmxnet3/vmxnet3_ethdev.c
> > +++ b/drivers/net/vmxnet3/vmxnet3_ethdev.c
> > @@ -1470,42 +1470,52 @@ vmxnet3_dev_stats_get(struct rte_eth_dev
> *dev, struct rte_eth_stats *stats)
> > struct vmxnet3_hw *hw = dev->data->dev_private;
> > struct UPT1_TxStats txStats;
> > struct UPT1_RxStats rxStats;
> > + uint64_t packets, bytes;
> >
> > VMXNET3_WRITE_BAR1_REG(hw, VMXNET3_REG_CMD,
> VMXNET3_CMD_GET_STATS);
> >
> > for (i = 0; i < hw->num_tx_queues; i++) {
> > vmxnet3_tx_stats_get(hw, i, &txStats);
> >
> > - stats->q_opackets[i] = txStats.ucastPktsTxOK +
> > + packets = txStats.ucastPktsTxOK +
> > txStats.mcastPktsTxOK +
> > txStats.bcastPktsTxOK;
> >
> > - stats->q_obytes[i] = txStats.ucastBytesTxOK +
> > + bytes = txStats.ucastBytesTxOK +
> > txStats.mcastBytesTxOK +
> > txStats.bcastBytesTxOK;
> >
> > - stats->opackets += stats->q_opackets[i];
> > - stats->obytes += stats->q_obytes[i];
> > + stats->opackets += packets;
> > + stats->obytes += bytes;
> > stats->oerrors += txStats.pktsTxError +
> txStats.pktsTxDiscard;
> > +
> > + if (i < RTE_ETHDEV_QUEUE_STAT_CNTRS) {
> > + stats->q_opackets[i] = packets;
> > + stats->q_obytes[i] = bytes;
> > + }
> > }
> >
> > for (i = 0; i < hw->num_rx_queues; i++) {
> > vmxnet3_rx_stats_get(hw, i, &rxStats);
> >
> > - stats->q_ipackets[i] = rxStats.ucastPktsRxOK +
> > + packets = rxStats.ucastPktsRxOK +
> > rxStats.mcastPktsRxOK +
> > rxStats.bcastPktsRxOK;
> >
> > - stats->q_ibytes[i] = rxStats.ucastBytesRxOK +
> > + bytes = rxStats.ucastBytesRxOK +
> > rxStats.mcastBytesRxOK +
> > rxStats.bcastBytesRxOK;
> >
> > - stats->ipackets += stats->q_ipackets[i];
> > - stats->ibytes += stats->q_ibytes[i];
> > -
> > - stats->q_errors[i] = rxStats.pktsRxError;
> > + stats->ipackets += packets;
> > + stats->ibytes += bytes;
> > stats->ierrors += rxStats.pktsRxError;
> > stats->imissed += rxStats.pktsRxOutOfBuf;
> > +
> > + if (i < RTE_ETHDEV_QUEUE_STAT_CNTRS) {
> > + stats->q_ipackets[i] = packets;
> > + stats->q_ibytes[i] = bytes;
> > + stats->q_errors[i] = rxStats.pktsRxError;
> > + }
> > }
> >
> > return 0;
>
> This fixes a bug in existing code of RTE_ETHDEV_QUEUE_STAT_CNTRS < num
> queues.
> Probably deserves its own patch with Fixes
Thanks for noticing, Stephen.
Ferruh also noticed, and has already applied such a patch:
https://patchwork.dpdk.org/project/dpdk/patch/20241104105220.1421305-1-mb@smartsharesystems.com/
The turnaround time was unusual quick on that one - it went in and out of Patchwork in a flash. Don't blink! ;-)
next prev parent reply other threads:[~2024-11-07 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 10:22 [PATCH] ethdev: TEST " Morten Brørup
2024-10-24 21:11 ` [PATCH v7] " Morten Brørup
2024-10-25 8:23 ` [PATCH v8] " Morten Brørup
2024-11-06 21:16 ` [TEST v9] " Morten Brørup
2024-11-06 22:02 ` [TEST v10] ethdev: " Morten Brørup
2024-11-06 23:25 ` Stephen Hemminger
2024-11-07 9:35 ` Morten Brørup [this message]
2024-11-07 9:26 ` [TEST v11] ethdev: test " Morten Brørup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=98CBD80474FA8B44BF855DF32C47DC35E9F88D@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).