From: Kurt Kanzenbach <kurt@linutronix.de>
To: Tan Tee Min <tee.min.tan@linux.intel.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Michael Sit Wei Hong <michael.wei.hong.sit@intel.com>,
Xiaoliang Yang <xiaoliang.yang_1@nxp.com>,
Wong Vee Khee <vee.khee.wong@linux.intel.com>,
Tan Tee Min <tee.min.tan@linux.intel.com>,
Ling Pei Lee <pei.lee.ling@intel.com>,
Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Voon Wei Feng <weifeng.voon@intel.com>,
Song Yoong Siang <yoong.siang.song@intel.com>,
Ong@vger.kernel.org, Boon Leong <boon.leong.ong@intel.com>,
Tan Tee Min <tee.min.tan@intel.com>
Subject: Re: [PATCH net 1/1] net: stmmac: disable Split Header (SPH) for Intel platforms
Date: Tue, 26 Apr 2022 15:58:56 +0200 [thread overview]
Message-ID: <8735i0ndy7.fsf@kurt> (raw)
In-Reply-To: <20220426074531.4115683-1-tee.min.tan@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 622 bytes --]
Hi,
On Tue Apr 26 2022, Tan Tee Min wrote:
> Based on DesignWare Ethernet QoS datasheet, we are seeing the limitation
> of Split Header (SPH) feature is not supported for Ipv4 fragmented packet.
> This SPH limitation will cause ping failure when the packets size exceed
> the MTU size. For example, the issue happens once the basic ping packet
> size is larger than the configured MTU size and the data is lost inside
> the fragmented packet, replaced by zeros/corrupted values, and leads to
> ping fail.
>
> So, disable the Split Header for Intel platforms.
Does this issue only apply on Intel platforms?
Thanks,
Kurt
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Kurt Kanzenbach <kurt@linutronix.de>
To: Tan Tee Min <tee.min.tan@linux.intel.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Michael Sit Wei Hong <michael.wei.hong.sit@intel.com>,
Xiaoliang Yang <xiaoliang.yang_1@nxp.com>,
Wong Vee Khee <vee.khee.wong@linux.intel.com>,
Tan Tee Min <tee.min.tan@linux.intel.com>,
Ling Pei Lee <pei.lee.ling@intel.com>,
Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Voon Wei Feng <weifeng.voon@intel.com>,
Song Yoong Siang <yoong.siang.song@intel.com>,
Ong@vger.kernel.org, Boon Leong <boon.leong.ong@intel.com>,
Tan Tee Min <tee.min.tan@intel.com>
Subject: Re: [PATCH net 1/1] net: stmmac: disable Split Header (SPH) for Intel platforms
Date: Tue, 26 Apr 2022 15:58:56 +0200 [thread overview]
Message-ID: <8735i0ndy7.fsf@kurt> (raw)
In-Reply-To: <20220426074531.4115683-1-tee.min.tan@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
Hi,
On Tue Apr 26 2022, Tan Tee Min wrote:
> Based on DesignWare Ethernet QoS datasheet, we are seeing the limitation
> of Split Header (SPH) feature is not supported for Ipv4 fragmented packet.
> This SPH limitation will cause ping failure when the packets size exceed
> the MTU size. For example, the issue happens once the basic ping packet
> size is larger than the configured MTU size and the data is lost inside
> the fragmented packet, replaced by zeros/corrupted values, and leads to
> ping fail.
>
> So, disable the Split Header for Intel platforms.
Does this issue only apply on Intel platforms?
Thanks,
Kurt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2022-04-26 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 7:45 [PATCH net 1/1] net: stmmac: disable Split Header (SPH) for Intel platforms Tan Tee Min
2022-04-26 13:58 ` Kurt Kanzenbach [this message]
2022-04-26 13:58 ` Kurt Kanzenbach
2022-04-28 1:55 ` Tan Tee Min
2022-04-28 1:55 ` Tan Tee Min
2022-04-28 7:05 ` Paolo Abeni
2022-04-28 7:05 ` Paolo Abeni
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=8735i0ndy7.fsf@kurt \
--to=kurt@linutronix.de \
--cc=Ong@vger.kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=bhupesh.sharma@linaro.org \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=michael.wei.hong.sit@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pei.lee.ling@intel.com \
--cc=peppe.cavallaro@st.com \
--cc=stable@vger.kernel.org \
--cc=tee.min.tan@intel.com \
--cc=tee.min.tan@linux.intel.com \
--cc=vee.khee.wong@linux.intel.com \
--cc=weifeng.voon@intel.com \
--cc=xiaoliang.yang_1@nxp.com \
--cc=yoong.siang.song@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.