From: David Miller <davem@davemloft.net>
To: skalluru@marvell.com
Cc: netdev@vger.kernel.org, aelior@marvell.com, mkalderon@marvell.com
Subject: Re: [PATCH net 1/1] qede: Fix internal loopback failure with jumbo mtu configuration
Date: Thu, 07 Mar 2019 09:43:53 -0800 (PST) [thread overview]
Message-ID: <20190307.094353.2006935561616629019.davem@davemloft.net> (raw)
In-Reply-To: <20190307155635.13968-1-skalluru@marvell.com>
From: Sudarsana Reddy Kalluru <skalluru@marvell.com>
Date: Thu, 7 Mar 2019 07:56:35 -0800
> Driver uses port-mtu as packet-size for the loopback traffic. This patch
> limits the max packet size to 1.5K to avoid data being split over multiple
> buffer descriptors (BDs) in cases where MTU > PAGE_SIZE.
>
> Signed-off-by: Sudarsana Reddy Kalluru <skalluru@marvell.com>
> Signed-off-by: Ariel Elior <aelior@marvell.com>
Applied.
prev parent reply other threads:[~2019-03-07 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 15:56 [PATCH net 1/1] qede: Fix internal loopback failure with jumbo mtu configuration Sudarsana Reddy Kalluru
2019-03-07 17:43 ` David Miller [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=20190307.094353.2006935561616629019.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aelior@marvell.com \
--cc=mkalderon@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=skalluru@marvell.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).