From: Dragos Tatulea <dtatulea@nvidia.com>
To: jiabin deng <dengjiabin2023@gmail.com>
Cc: netdev@vger.kernel.org, saeedm@nvidia.com, tariqt@nvidia.com,
mbloch@nvidia.com, linux-kernel@vger.kernel.org
Subject: Re: mlx5e:zero-prefix corruption during TCP DMA-BUF RX - help requested
Date: Fri, 23 Oct 2026 15:14:59 +0200 [thread overview]
Message-ID: <d6c14ede-1cfd-4800-a8bf-5093ab8c000a@nvidia.com> (raw)
In-Reply-To: <CAFxp=AYqVgR_Eahz2QsC=cCdxo5GmTwdHcgBdXRGf9P+v0OJxQ@mail.gmail.com>
On 21.10.26 07:19, jiabin deng wrote:
> Hi Dragos,
>
> I applied your suggested change to `rq_end_pad_mode()` on the receiver
> and reran the standalone GPU-memory reproducer I sent previously. With
> MTU set to 1500, the single-direction test covered eight message
> sizes, with 50 transfers per size, for a total of 400 transfers.
>
> All 400 transfers completed successfully. Full payload comparisons
> found zero failing cases, zero incorrect bytes, and zero corrupted
> intervals. The zero-prefix corruption observed in the earlier tests
> did not recur in this patched run.
>
> Thank you for continuing to investigate this issue and for suggesting
> the fix. I also greatly appreciate the time and effort you and the
> other maintainers dedicate to the open-source community. As a student,
> I am excited to have the opportunity to contribute to the community
> and to learn from this process.
>
Thank you for your good analysis and fast response!
> I would be happy to help prepare a formal patch with the test results.
> Would you prefer to submit the fix yourself, or would it be helpful
> for me to prepare and submit it based on your suggested change?
>
I am still waiting for input from the HW folks to understand if this
change is needed for all SHAMPO cases or only specific P2P DMA
cases.
I think you should submit the fix as you did most of the work. Just
give me some time to check the above. I'll ping you hopefully next
week.
Thanks,
Dragos
prev parent reply other threads:[~2026-10-23 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 1:49 jiabin deng
2026-09-15 12:21 ` Dragos Tatulea
2026-09-18 6:06 ` jiabin deng
2026-09-29 9:49 ` Dragos Tatulea
2026-10-08 6:48 ` jiabin deng
2026-10-20 10:56 ` Dragos Tatulea
2026-10-21 5:19 ` jiabin deng
2026-10-23 13:14 ` Dragos Tatulea [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=d6c14ede-1cfd-4800-a8bf-5093ab8c000a@nvidia.com \
--to=dtatulea@nvidia.com \
--cc=dengjiabin2023@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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
all inboxes | Powered by JetHome®