From: Florian Fainelli <f.fainelli@gmail.com>
To: David Laight <David.Laight@ACULAB.COM>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"vivien.didelot@savoirfairelinux.com"
<vivien.didelot@savoirfairelinux.com>
Subject: Re: [PATCH net-next v2 1/3] net: bgmac: Pad packets to a minimum size
Date: Fri, 10 Nov 2017 09:55:55 -0800 [thread overview]
Message-ID: <c7687d0a-bbe8-0aff-efdb-c73392b4206a@gmail.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DD00B846B@AcuExch.aculab.com>
On 11/10/2017 03:10 AM, David Laight wrote:
> From: Florian Fainelli
>> Sent: 09 November 2017 22:35
>>
>> In preparation for enabling Broadcom tags with b53, pad packets to a
>> minimum size of 64 bytes (sans FCS) in order for the Broadcom switch to
>> accept ingressing frames. Without this, we would typically be able to
>> DHCP, but not resolve with ARP because packets are too small and get
>> rejected by the switch.
>>
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>> drivers/net/ethernet/broadcom/bgmac.c | 13 +++++++++++++
>> 1 file changed, 13 insertions(+)
>>
>> diff --git a/drivers/net/ethernet/broadcom/bgmac.c b/drivers/net/ethernet/broadcom/bgmac.c
>> index 48d672b204a4..5130fc96940d 100644
>> --- a/drivers/net/ethernet/broadcom/bgmac.c
>> +++ b/drivers/net/ethernet/broadcom/bgmac.c
>> @@ -127,6 +127,8 @@ bgmac_dma_tx_add_buf(struct bgmac *bgmac, struct bgmac_dma_ring *ring,
>> dma_desc->ctl1 = cpu_to_le32(ctl1);
>> }
>>
>> +#define ENET_BRCM_TAG_LEN 4
>> +
>> static netdev_tx_t bgmac_dma_tx_add(struct bgmac *bgmac,
>> struct bgmac_dma_ring *ring,
>> struct sk_buff *skb)
>> @@ -139,6 +141,16 @@ static netdev_tx_t bgmac_dma_tx_add(struct bgmac *bgmac,
>> u32 flags;
>> int i;
>>
>> + /* The Ethernet switch we are interfaced with needs packets to be at
>> + * least 64 bytes (including FCS) otherwise they will be discarded when
>> + * they enter the switch port logic. When Broadcom tags are enabled, we
>> + * need to make sure that packets are at least 68 bytes
>> + * (including FCS and tag) because the length verification is done after
>> + * the Broadcom tag is stripped off the ingress packet.
>> + */
>
> I think that that would be better as:
> /* Ethernet packets are padded to 64 bytes (including FCS).
> * If 'Broadcom tags' are enabled they must still be 64 bytes
> * long after the 4 byte tag is removed.
> * Since the hardware doesn't do it, we must pad them before
> * transmit.
> */
>
> Which seems to be to be a bug in the chip.
The same comment exists in drivers/net/ethernet/broadcom/bcmsysport.c,
and almost 4 years ago, you made pretty much the same type of drive-by
review, so no, I am not changing any of that comment which explains
exactly what is going on.
>
>> + if (skb_put_padto(skb, ETH_ZLEN + ENET_BRCM_TAG_LEN))
>> + goto err_stats;
>> +
>
> But you shouldn't overpad packets that don't have the extra tag.
I don't see a point in putting a netdev_uses_dsa() check to know whether
we should pad or not to an extra ENET_BRCM_TAG_LEN, the packets are
already hot in cache at that point, and they are small, so sure, this
will put some more cache pressure for host originating 64bytes packets,
but I don't see this being a real use case (except for benchmarks).
--
Florian
next prev parent reply other threads:[~2017-11-10 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 22:34 [PATCH net-next v2 0/3] net: dsa: b53: Turn on Broadcom tags Florian Fainelli
2017-11-09 22:34 ` [PATCH net-next v2 1/3] net: bgmac: Pad packets to a minimum size Florian Fainelli
2017-11-10 11:10 ` David Laight
2017-11-10 17:55 ` Florian Fainelli [this message]
2017-11-09 22:34 ` [PATCH net-next v2 2/3] net: dsa: b53: Stop using dev->cpu_port incorrectly Florian Fainelli
2017-11-09 22:34 ` [PATCH net-next v2 3/3] net: dsa: b53: Turn on Broadcom tags Florian Fainelli
2017-11-10 18:01 ` [PATCH net-next v2 0/3] " Florian Fainelli
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=c7687d0a-bbe8-0aff-efdb-c73392b4206a@gmail.com \
--to=f.fainelli@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).