From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>, <dev@dpdk.org>
Subject: Re: [PATCH v2] net/cxgbe: track packets dropped by TP due to congestion
Date: Tue, 17 May 2022 17:52:09 +0100 [thread overview]
Message-ID: <fed92a61-592e-61d1-0f1b-943e0923d288@xilinx.com> (raw)
In-Reply-To: <61ae717665c2f4e38712652bec2f9d0fe5ca7d32.1651842841.git.rahul.lakkireddy@chelsio.com>
On 5/6/2022 2:18 PM, Rahul Lakkireddy wrote:
> Transport Processor (TP) on the NIC delivers the incoming packets
> from the wire to NIC's DMA engine to place the packets in Rx buffers.
> TP sends signal towards the Multi-Port Switch (MPS) near the MAC when
> the Rxqs run out of Rx buffers posted by driver. These MPS buffer drop
> stats are already accounted for in imissed counters. However, if a
> large number of Rxqs run out of Rx buffers simultaneously, then the
> TP can start dropping packets by itself when there is heavy congestion
> on the channel and hence could not inform to the MPS. So, track these
> packets dropped by TP in imissed counters. Also add xstats for these
> counters.
>
> Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2022-05-17 16:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 22:24 [PATCH 0/5] net/cxgbe: updates and bug fixes Rahul Lakkireddy
2022-04-18 22:24 ` [PATCH 1/5] net/cxgbe: fill correct port info in mbufs for Rx Rahul Lakkireddy
2022-04-18 22:24 ` [PATCH 2/5] net/cxgbe: fix Tx queue stuck with mbuf chain coalescing Rahul Lakkireddy
2022-04-18 22:24 ` [PATCH 3/5] net/cxgbe: simplify Rx payload buffer size posting Rahul Lakkireddy
2022-04-18 22:24 ` [PATCH 4/5] net/cxgbe: track packets dropped by TP due to congestion Rahul Lakkireddy
2022-05-05 16:28 ` Ferruh Yigit
2022-05-06 11:09 ` Rahul Lakkireddy
2022-05-06 12:32 ` Ferruh Yigit
2022-05-06 13:18 ` [PATCH v2] " Rahul Lakkireddy
2022-05-17 16:52 ` Ferruh Yigit [this message]
2022-04-18 22:24 ` [PATCH 5/5] net/cxgbe: read firmware configuration file from filesystem Rahul Lakkireddy
2022-05-05 16:29 ` Ferruh Yigit
2022-05-05 16:36 ` Ferruh Yigit
2022-05-06 11:36 ` Rahul Lakkireddy
2022-05-10 9:02 ` Thomas Monjalon
2022-05-10 14:11 ` Rahul Lakkireddy
2022-05-10 14:30 ` Thomas Monjalon
2022-05-10 15:05 ` Rahul Lakkireddy
2022-05-10 16:20 ` Thomas Monjalon
2022-05-16 10:27 ` [PATCH v2] " Rahul Lakkireddy
2022-05-16 11:06 ` Ferruh Yigit
2022-05-16 11:56 ` Rahul Lakkireddy
2022-05-16 14:05 ` Ferruh Yigit
2022-05-16 19:34 ` [PATCH v3] " Rahul Lakkireddy
2022-05-17 16:52 ` Ferruh Yigit
2022-05-05 16:29 ` [PATCH 0/5] net/cxgbe: updates and bug fixes Ferruh Yigit
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=fed92a61-592e-61d1-0f1b-943e0923d288@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=dev@dpdk.org \
--cc=rahul.lakkireddy@chelsio.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).