From: Ansuel Smith <ansuelsmth@gmail.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [RFC PATCH net-next 0/7] DSA master state tracking
Date: Thu, 9 Dec 2021 19:34:45 +0100 [thread overview]
Message-ID: <61b24c47.1c69fb81.3e958.1990@mx.google.com> (raw)
In-Reply-To: <20211209175720.cpifrbibghapm7eo@skbuf>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
On Thu, Dec 09, 2021 at 05:57:20PM +0000, Vladimir Oltean wrote:
> On Thu, Dec 09, 2021 at 06:44:38PM +0100, Ansuel Smith wrote:
> > Ok will send a pcap. Any preferred way to send it?
>
> Email attachment should be fine.
This is a pcap done on the cpu port eth0.
All the packet with lenght 60 are the Ethernet mdio packet.
The capture is done with no cable connected so don't know why there are
some broadcast for ipv6.
Special care about the fact that the qca tag is always present in the
EtherType.
Mdio request qca tag 8181
mdio ack qca tag b887
(I should really investigate the extra packet... In theory they are not
sent (and i remember checking this) by the tagger as they have bit 5:4
set to 0x2... From Documentation these bit are reserved and in our code
we always set them to zero. The switch by itself sends broadcast tagged
packet and respond itself?)
I attached the pcap.
--
Ansuel
[-- Attachment #2: pkts.pcap --]
[-- Type: application/vnd.tcpdump.pcap, Size: 29944 bytes --]
prev parent reply other threads:[~2021-12-09 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 22:32 [RFC PATCH net-next 0/7] DSA master state tracking Vladimir Oltean
2021-12-08 22:32 ` [RFC PATCH net-next 1/7] net: dsa: only bring down user ports assigned to a given DSA master Vladimir Oltean
2021-12-08 22:32 ` [RFC PATCH net-next 2/7] net: dsa: refactor the NETDEV_GOING_DOWN master tracking into separate function Vladimir Oltean
2021-12-08 22:32 ` [RFC PATCH net-next 3/7] net: dsa: use dsa_tree_for_each_user_port in dsa_tree_master_going_down() Vladimir Oltean
2021-12-08 22:32 ` [RFC PATCH net-next 4/7] net: dsa: provide switch operations for tracking the master state Vladimir Oltean
2021-12-08 22:32 ` [RFC PATCH net-next 5/7] net: dsa: stop updating master MTU from master.c Vladimir Oltean
2021-12-08 22:32 ` [RFC PATCH net-next 6/7] net: dsa: hold rtnl_mutex when calling dsa_master_{setup,teardown} Vladimir Oltean
2021-12-08 22:32 ` [RFC PATCH net-next 7/7] net: dsa: replay master state events in dsa_tree_{setup,teardown}_master Vladimir Oltean
2021-12-09 3:05 ` [RFC PATCH net-next 0/7] DSA master state tracking Ansuel Smith
2021-12-09 14:28 ` Vladimir Oltean
2021-12-09 14:44 ` Ansuel Smith
2021-12-09 17:33 ` Vladimir Oltean
2021-12-09 17:44 ` Ansuel Smith
2021-12-09 17:56 ` Vladimir Oltean
2021-12-09 18:16 ` Ansuel Smith
2021-12-09 17:57 ` Vladimir Oltean
2021-12-09 18:34 ` Ansuel Smith [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=61b24c47.1c69fb81.3e958.1990@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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.