mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jose Abreu <jose.abreu@synopsys.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>,
	"David S. Miller" <davem@davemloft.net>,
	Giuseppe Cavallaro <peppe.cavallaro@st.com>,
	Alexandre Torgue <alexandre.torgue@st.com>,
	Jose Abreu <jose.abreu@synopsys.com>,
	Thor Thayer <thor.thayer@linux.intel.com>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Aaro Koskinen <aaro.koskinen@nokia.com>
Subject: Re: [PATCH 2/2] net: stmmac: fix jumbo frame sending with non-linear skbs
Date: Fri, 15 Mar 2019 09:50:15 +0000	[thread overview]
Message-ID: <08a089e6-16a7-1f6c-e356-a5bcea360078@synopsys.com> (raw)
In-Reply-To: <20190314194320.25566-2-aaro.koskinen@iki.fi>

On 3/14/2019 7:43 PM, Aaro Koskinen wrote:
> From: Aaro Koskinen <aaro.koskinen@nokia.com>
> 
> When sending non-linear skbs with jumbo frames, we set up the non-paged
> data and mark that as a last segment, although the paged fragments are
> also prepared. This will stall the TX queue and trigger a watchdog warning
> (a simple reproducer is to run an iperf client mode TCP test with a large
> MTU - networking fails instantly).
> 
> Fix by checking if the skb is non-linear.
> 
> Signed-off-by: Aaro Koskinen <aaro.koskinen@nokia.com>

Acked-by: Jose Abreu <joabreu@synopsys.com>

Thanks,
Jose Miguel Abreu

  reply	other threads:[~2019-03-15  9:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 19:43 [PATCH 1/2] net: stmmac: don't set own bit too early for jumbo frames Aaro Koskinen
2019-03-14 19:43 ` [PATCH 2/2] net: stmmac: fix jumbo frame sending with non-linear skbs Aaro Koskinen
2019-03-15  9:50   ` Jose Abreu [this message]
2019-03-15 18:39   ` David Miller
2019-03-15  8:45 ` [PATCH 1/2] net: stmmac: don't set own bit too early for jumbo frames Sergei Shtylyov
2019-03-15  9:47 ` Jose Abreu
2019-03-15 18:39 ` David Miller

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=08a089e6-16a7-1f6c-e356-a5bcea360078@synopsys.com \
    --to=jose.abreu@synopsys.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=aaro.koskinen@nokia.com \
    --cc=alexandre.torgue@st.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    --cc=thor.thayer@linux.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 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®