From: Claudiu Manoil <claudiu.manoil@freescale.com>
To: voncken <cedric.voncken@acksys.fr>
Cc: <netdev@vger.kernel.org>
Subject: Re: Gianfar : Drop a long frame
Date: Wed, 30 Jan 2013 17:55:44 +0200 [thread overview]
Message-ID: <51094280.8060701@freescale.com> (raw)
In-Reply-To: <001a01cdfeef$cdc5bee0$69513ca0$@acksys.fr>
On 1/30/2013 3:43 PM, voncken wrote:
> Hi Claudiu,
>
> I have a problem with the gianfar driver.
>
> My test conditions are:
> - Disable rxvlan hardware acceleration (ethtool -K ethx
> rxvlan off)
> - Receive frame contains a VLAN tag and with a frame len set
> to the MTU (1500 bytes).
>
> In this condition, when I received a long frame the bdp->length is
> set to 1538 bytes.
> I guess it is composed of:
> 1500 bytes: L3 data bytes
> + 14 bytes: Ethernet header
> + 4 bytes: Vlan Tag header
> + 8 bytes: FCB structure size GMAC_FCB_LEN
> + 8 bytes: eTSEC padding
> + 4 bytes: Frames CRC (FCS)
>
> The Maximum frame len is set to 1536 because the function
> gfar_change_mtu does not integrate the FCS in the computed frame size.
> In this condition this frame is dropped with the test line 2792
> function gfar_clean_rx_ring
> if (unlikely(!(bdp->status & RXBD_ERR) &&
> bdp->length > priv->rx_buffer_size))
> bdp->status = RXBD_LARGE;
>
> How I can receive this frame correctly?
>
> Best regards
>
> Cedric Voncken | R&d Engineer
Hi Cedric Voncken,
Is the 802.1Q support activated on the receiving host? (see
CONFIG_VLAN_8021Q)
next prev parent reply other threads:[~2013-01-30 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 13:43 Gianfar : Drop a long frame voncken
2013-01-30 15:55 ` Claudiu Manoil [this message]
2013-01-30 16:27 ` voncken
2013-01-31 8:50 ` Claudiu Manoil
2013-01-31 14:13 ` voncken
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=51094280.8060701@freescale.com \
--to=claudiu.manoil@freescale.com \
--cc=cedric.voncken@acksys.fr \
--cc=netdev@vger.kernel.org \
/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).