DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>
To: Joshua Washington <joshwash@google.com>
Cc: Ferruh Yigit <ferruh.yigit@amd.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 23:20:57 +0530	[thread overview]
Message-ID: <CA++LmPVnDygKNXHgLizyPd=cr5oOqcYOGQO8KwWUOBFqgutk+A@mail.gmail.com> (raw)
In-Reply-To: <CALuQH+X-92jt25Jd0C6FuVQkRA5svH1srpUVwGedhsFQDCUd-g@mail.gmail.com>

Hi Josh,

Updated the patch
(https://patches.dpdk.org/project/dpdk/patch/1722534481-2405601-1-git-send-email-tathagat.dpdk@gmail.com/),
please ACK if it looks good.

Thanks!

On Thu, Aug 1, 2024 at 9:55 PM Joshua Washington <joshwash@google.com> wrote:
>
> 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.

  reply	other threads:[~2024-08-01 17:51 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
2024-08-01 17:50     ` Tathagat Priyadarshi [this message]
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='CA++LmPVnDygKNXHgLizyPd=cr5oOqcYOGQO8KwWUOBFqgutk+A@mail.gmail.com' \
    --to=tathagat.dpdk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=joshwash@google.com \
    --cc=rushilg@google.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).