DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>, <dev@dpdk.org>
Subject: Re: [PATCH 0/5] net/cxgbe: updates and bug fixes
Date: Thu, 5 May 2022 17:29:12 +0100	[thread overview]
Message-ID: <9231e643-a403-1d4f-fe90-1597e25133cb@xilinx.com> (raw)
In-Reply-To: <cover.1650297776.git.rahul.lakkireddy@chelsio.com>

On 4/18/2022 11:24 PM, Rahul Lakkireddy wrote:
> This series of patches add the following updates and bug fixes to
> the cxgbe PMD.
> 
> Patch 1 fixes an issue with wrong port id being filled in mbufs
> allocated in Rx path.
> 
> Patch 2 fixes an issue with Txq getting stuck when trying to coalesce
> mbufs with chains.
> 
> Patch 3 reworks and simplifies the code for posting mbufs and their
> payload buffer sizes to hardware in Rx path.
> 
> Patch 4 adds support to track packets in Rx path dropped due to
> congestion at Rx queues that may not get propagated to the rest
> of the Rx pipeline.
> 
> Patch 5 adds support to read firmware configuration file from
> /lib/firmware/cxgb4/ to allow changing firmware parameters without
> having to flash the configuration file onto the adapter.
> 
> Thanks,
> Rahul
> 
> Rahul Lakkireddy (5):
>    net/cxgbe: fill correct port info in mbufs for Rx
>    net/cxgbe: fix Tx queue stuck with mbuf chain coalescing
>    net/cxgbe: simplify Rx payload buffer size posting
>    net/cxgbe: track packets dropped by TP due to congestion
>    net/cxgbe: read firmware configuration file from filesystem
> 

Except from 4/5 & 5/5,
Series applied to dpdk-next-net/main, thanks.

Please check comments for 4/5 & 5/5. Since patches are independent, I 
think it would be OK to send a new series for remaining patches.

Thanks,
ferruh

      parent reply	other threads:[~2022-05-05 16:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 22:24 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
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 ` Ferruh Yigit [this message]

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=9231e643-a403-1d4f-fe90-1597e25133cb@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).