All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [Query]: DSA Understanding
Date: Thu, 9 Aug 2018 19:23:34 +0200	[thread overview]
Message-ID: <20180809172334.GA25449@lunn.ch> (raw)
In-Reply-To: <CA+V-a8uvA2rZ8gGFwXH835-vEs3G+cAygNLAi3uC1Sf+LpW_jQ@mail.gmail.com>

> Its coming from the switch lan4 I have attached the png, where
> C4:F3:12:08:FE:7F is
> the mac of lan4, which is broadcast to ff:ff:ff:ff:ff:ff, which is
> causing rx counter on
> PC to go up.

So, big packets are making it from the switch to the PC. But the small
ARP packets are not.

This is what Florian was suggesting.

ARP packets are smaller than 64 bytes, which is the minimum packet
size for Ethernet. Any packets smaller than 64 bytes are called runt
packets. They have to be padded upto 64 bytes in order to make them
valid. Otherwise the destination, or any switch along the path, might
throw them away.

What could be happening is that the CSPW driver or hardware is padding
the packet to 64 bytes. But that packet has a DSA header in it. The
switch removes the header, recalculate the checksum and sends the
packet. It is now either 4 or 8 bytes smaller, depending on what DSA
header was used. It then becomes a runt packet.

Florian had to fix this problem recently.

http://patchwork.ozlabs.org/patch/836534/

You probably need something similar for the cpsw.

    Andrew

  reply	other threads:[~2018-08-09 19:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25  8:39 [Query]: DSA Understanding Lad, Prabhakar
2018-07-25 16:19 ` Andrew Lunn
2018-07-26  7:38   ` Lad, Prabhakar
2018-07-26 14:08     ` Andrew Lunn
2018-07-26 15:20       ` Lad, Prabhakar
2018-07-26 15:39         ` Andrew Lunn
2018-08-02  8:13           ` Lad, Prabhakar
2018-08-02 14:45             ` Andrew Lunn
2018-08-02 14:58               ` Lad, Prabhakar
2018-08-02 16:05                 ` Andrew Lunn
2018-08-02 16:24                   ` Florian Fainelli
2018-08-09 11:33                     ` Lad, Prabhakar
2018-08-09 12:08                       ` Andrew Lunn
2018-08-09 11:31                   ` Lad, Prabhakar
2018-08-09 12:01                     ` Andrew Lunn
2018-08-09 12:45                       ` Lad, Prabhakar
2018-08-09 12:56                         ` Andrew Lunn
2018-08-09 15:07                           ` Lad, Prabhakar
2018-08-09 15:35                             ` Andrew Lunn
2018-08-09 16:03                               ` Lad, Prabhakar
2018-08-09 17:23                                 ` Andrew Lunn [this message]
2018-08-10 11:26                                   ` Lad, Prabhakar
2018-08-10 17:36                                     ` Florian Fainelli
2018-08-13 11:06                                       ` Lad, Prabhakar
2018-08-13 13:38                                         ` Andrew Lunn
2018-08-13 15:58                                           ` Lad, Prabhakar
2018-08-13 18:57                                             ` Florian Fainelli
2018-08-14 11:49                                               ` Lad, Prabhakar

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=20180809172334.GA25449@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=netdev@vger.kernel.org \
    --cc=prabhakar.csengg@gmail.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 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.