From: Martin Spinler <spinler@cesnet.cz>
To: Ferruh Yigit <ferruh.yigit@intel.com>, dev@dpdk.org
Subject: Re: [PATCH 3/6] drivers/nfb: do not report zero-sized TX burst
Date: Mon, 14 Feb 2022 17:53:14 +0100 [thread overview]
Message-ID: <9e543fe223f78405a72d36c2d244316510f9f169.camel@cesnet.cz> (raw)
In-Reply-To: <9ae7a914-fc0f-f2d9-5e48-00c56676eab1@intel.com>
On Mon, 2022-02-14 at 13:35 +0000, Ferruh Yigit wrote:
> On 2/14/2022 11:25 AM, spinler@cesnet.cz wrote:
> > From: Martin Spinler <spinler@cesnet.cz>
> >
> > Zero-sized TX burst floods the log no more.
> >
>
> If you want this patch to be backported, you can update
> commit log as fix and add fixes & stable tags.
I don't think it is a fix, rather an unplesant behaviour in a specific
application. It doesn't happen in the test-pmd app.
>
> > Signed-off-by: Martin Spinler <spinler@cesnet.cz>
> > ---
> > drivers/net/nfb/nfb_tx.h | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/nfb/nfb_tx.h b/drivers/net/nfb/nfb_tx.h
> > index d3cbe3e6b3..910020e9e9 100644
> > --- a/drivers/net/nfb/nfb_tx.h
> > +++ b/drivers/net/nfb/nfb_tx.h
> > @@ -136,7 +136,10 @@ nfb_eth_ndp_tx(void *queue,
> >
> > struct ndp_packet packets[nb_pkts];
> >
> > - if (unlikely(ndp->queue == NULL || nb_pkts == 0)) {
> > + if (unlikely(nb_pkts == 0))
> > + return 0;
> > +
> > + if (unlikely(ndp->queue == NULL)) {
> > RTE_LOG(ERR, PMD, "TX invalid arguments!\n");
> > return 0;
> > }
>
next prev parent reply other threads:[~2022-02-14 16:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 11:25 [PATCH 1/6] net/nfb: add missing libfdt dependency for build spinler
2022-02-14 11:25 ` [PATCH 2/6] drivers/nfb: fix array indexes in deinit functions spinler
2022-02-14 13:34 ` Ferruh Yigit
2022-02-14 16:52 ` Martin Spinler
2022-02-14 11:25 ` [PATCH 3/6] drivers/nfb: do not report zero-sized TX burst spinler
2022-02-14 13:35 ` Ferruh Yigit
2022-02-14 16:53 ` Martin Spinler [this message]
2022-02-14 17:34 ` Ferruh Yigit
2022-02-14 11:25 ` [PATCH 4/6] drivers/nfb: use RTE_ETH_RX_OFFLOAD_TIMESTAMP flag spinler
2022-02-14 11:25 ` [PATCH 5/6] drivers/nfb: fix multicast/promiscuous mode switching spinler
2022-02-14 13:36 ` Ferruh Yigit
2022-02-14 16:53 ` Martin Spinler
2022-02-14 11:25 ` [PATCH 6/6] drivers/nfb: add support for more MAC addresses spinler
2022-02-14 13:37 ` Ferruh Yigit
2022-02-14 16:53 ` Martin Spinler
2022-02-14 17:54 ` Ferruh Yigit
2022-02-15 13:02 ` Martin Spinler
2022-02-14 13:36 ` [PATCH 1/6] net/nfb: add missing libfdt dependency for build Ferruh Yigit
2022-02-14 16:53 ` Martin Spinler
2022-02-15 12:55 ` [PATCH v2 0/5] " spinler
2022-02-15 12:55 ` [PATCH v2 1/5] net/nfb: fix array indexes in deinit functions spinler
2022-02-15 12:55 ` [PATCH v2 2/5] net/nfb: do not report zero-sized TX burst spinler
2022-02-15 12:55 ` [PATCH v2 3/5] net/nfb: use RTE_ETH_RX_OFFLOAD_TIMESTAMP flag spinler
2022-02-15 12:55 ` [PATCH v2 4/5] net/nfb: fix multicast/promiscuous mode switching spinler
2022-02-15 12:55 ` [PATCH v2 5/5] net/nfb: add support for more MAC addresses spinler
2022-02-15 13:55 ` [PATCH v2 0/5] net/nfb: add missing libfdt dependency for build Ferruh Yigit
2022-02-15 13:57 ` Martin Spinler
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=9e543fe223f78405a72d36c2d244316510f9f169.camel@cesnet.cz \
--to=spinler@cesnet.cz \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
/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).