netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: alexander.sverdlin@nokia.com
Cc: netdev@vger.kernel.org, alexander.sverdlin@nsn.com,
	steven.hill@cavium.com
Subject: Re: [PATCH] octeon_mgmt: Fix MIX registers configuration on MTU setup
Date: Wed, 18 Jul 2018 13:13:41 +0900 (KST)	[thread overview]
Message-ID: <20180718.131341.1949854699503730806.davem@davemloft.net> (raw)
In-Reply-To: <20180713153150.2414-1-alexander.sverdlin@nokia.com>

From: Alexander Sverdlin <alexander.sverdlin@nokia.com>
Date: Fri, 13 Jul 2018 17:31:50 +0200

> From: Alexander Sverdlin <alexander.sverdlin@nsn.com>
> 
> octeon_mgmt driver doesn't drop RX frames that are 1-4 bytes bigger than
> MTU set for the corresponding interface. The problem is in the
> AGL_GMX_RX0/1_FRM_MAX register setting, which should not account for VLAN
> tagging.
> 
> According to Octeon HW manual:
> "For tagged frames, MAX increases by four bytes for each VLAN found up to a
> maximum of two VLANs, or MAX + 8 bytes."
> 
> OCTEON_FRAME_HEADER_LEN "define" is fine for ring buffer management, but
> should not be used for AGL_GMX_RX0/1_FRM_MAX.
> 
> The problem could be easily reproduced using "ping" command. If affected
> system has default MTU 1500, other host (having MTU >= 1504) can
> successfully "ping" the affected system with payload size 1473-1476,
> resulting in IP packets of size 1501-1504 accepted by the mgmt driver.
> Fixed system still accepts IP packets of 1500 bytes even with VLAN tagging,
> because the limits are lifted in HW as expected, for every VLAN tag.
> 
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@nokia.com>

Applied, thank you.

      reply	other threads:[~2018-07-18  4:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13 15:31 [PATCH] octeon_mgmt: Fix MIX registers configuration on MTU setup Alexander Sverdlin
2018-07-18  4:13 ` 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=20180718.131341.1949854699503730806.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alexander.sverdlin@nokia.com \
    --cc=alexander.sverdlin@nsn.com \
    --cc=netdev@vger.kernel.org \
    --cc=steven.hill@cavium.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).