From: "voncken" <cedric.voncken@acksys.fr>
To: "'Claudiu Manoil'" <claudiu.manoil@freescale.com>
Cc: <netdev@vger.kernel.org>
Subject: Gianfar : Drop a long frame
Date: Wed, 30 Jan 2013 14:43:36 +0100 [thread overview]
Message-ID: <001a01cdfeef$cdc5bee0$69513ca0$@acksys.fr> (raw)
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
----------------------------------------------------------------------------
------------------------------
T : +33 1 30 56 46 52
cedric.voncken@acksys.fr | www.acksys.fr
----------------------------------------------------------------------------
------------------------------
ZA Val Joyeux - 10 rue des Entrepreneurs - 78450 VILLEPREUX - France
----------------------------------------------------------------------------
----------
next reply other threads:[~2013-01-30 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 13:43 voncken [this message]
2013-01-30 15:55 ` Gianfar : Drop a long frame Claudiu Manoil
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='001a01cdfeef$cdc5bee0$69513ca0$@acksys.fr' \
--to=cedric.voncken@acksys.fr \
--cc=claudiu.manoil@freescale.com \
--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 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.