From: Joshua Washington <joshwash@google.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>,
Rushil Gupta <rushilg@google.com>,
dev@dpdk.org, Varun Lakkur Ambaji Rao <varun.la@gmail.com>
Subject: Re: [PATCH] net/gve : Update EOP bit in txd rte_mbuf chain
Date: Thu, 1 Aug 2024 09:24:53 -0700 [thread overview]
Message-ID: <CALuQH+X-92jt25Jd0C6FuVQkRA5svH1srpUVwGedhsFQDCUd-g@mail.gmail.com> (raw)
In-Reply-To: <6613e5f2-4e58-47d9-a986-f57255dc68b1@amd.com>
[-- Attachment #1: Type: text/plain, Size: 275 bytes --]
Hi, can we try to serialize these patches? Let's fix the multidescriptor
packets issue present in the driver first (ensuring that the entire
descriptor is written each time). The TSO support is an entirely new
feature and should likely not be backported to stable releases.
[-- Attachment #2: Type: text/html, Size: 303 bytes --]
next prev parent reply other threads:[~2024-08-01 16:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 16:38 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 [this message]
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
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=CALuQH+X-92jt25Jd0C6FuVQkRA5svH1srpUVwGedhsFQDCUd-g@mail.gmail.com \
--to=joshwash@google.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=rushilg@google.com \
--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).