From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>,
stephen@networkplumber.org, dev@dpdk.org
Cc: stable@dpdk.org, Varun Lakkur Ambaji Rao <varun.la@gmail.com>
Subject: Re: [PATCH v5] net/gve : Update EOP & csum bit in txd rte_mbuf chain
Date: Wed, 7 Aug 2024 10:39:14 +0100 [thread overview]
Message-ID: <186c92b4-b26b-449e-a5db-2a388fa73857@amd.com> (raw)
In-Reply-To: <1722575288-2408630-1-git-send-email-tathagat.dpdk@gmail.com>
On 8/2/2024 6:08 AM, Tathagat Priyadarshi wrote:
> The EOP and csum bit was not set for all the packets in mbuf chain
> causing packet transmission stalls for packets split across
> mbuf in chain.
>
> Fixes: 4022f99 ("net/gve: support basic Tx data path for DQO")
> Cc: stable@dpdk.org
>
> Signed-off-by: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>
> Signed-off-by: Varun Lakkur Ambaji Rao <varun.la@gmail.com>
>
> Acked-by: Joshua Washington <joshwash@google.com>
>
Updated commit log slightly, please check the merged version.
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-08-07 9:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 16:38 [PATCH] net/gve : Update EOP " Tathagat Priyadarshi
2024-07-31 20:30 ` Joshua Washington
2024-08-01 10:23 ` Tathagat Priyadarshi
2024-08-01 11:16 ` Ferruh Yigit
2024-08-01 16:24 ` Joshua Washington
2024-08-01 17:50 ` Tathagat Priyadarshi
2024-08-01 11:31 ` [PATCH v2] " Tathagat Priyadarshi
2024-08-01 17:27 ` [PATCH v3] net/gve : Update EOP & csum " Tathagat Priyadarshi
2024-08-01 18:54 ` Stephen Hemminger
2024-08-01 18:58 ` Tathagat Priyadarshi
2024-08-01 17:48 ` [PATCH v4] " Tathagat Priyadarshi
2024-08-02 5:08 ` [PATCH v5] " Tathagat Priyadarshi
2024-08-02 5:10 ` Tathagat Priyadarshi
2024-08-06 14:44 ` Tathagat Priyadarshi
2024-08-07 7:36 ` Ferruh Yigit
2024-08-07 9:39 ` 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=186c92b4-b26b-449e-a5db-2a388fa73857@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=tathagat.dpdk@gmail.com \
--cc=varun.la@gmail.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).