From: Andrew Lunn <andrew@lunn.ch>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dsa: tag_rtl4_a: Bump min packet size
Date: Sun, 29 Oct 2023 18:35:49 +0100 [thread overview]
Message-ID: <6c10edf1-dad1-4a4f-ae0e-42b17febbd5d@lunn.ch> (raw)
In-Reply-To: <CACRpkdbyMEqjW1a9oK-GM2_XL0famH1RgSXW-fQLszn9t9UhWw@mail.gmail.com>
> The switch is pretty bogus, all documentation we have of it is a vendor
> code drop, no data sheet. The format for ingress and egress tags
> was discovered using trial-and-error.
The code drop does not include tagging? Does the code drop also pad to
full size Ethernet frames?
I still think it would be good to do some systematic testing to figure
out if there is any pattern to the drops.
Andrew
next prev parent reply other threads:[~2023-10-29 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 20:21 [PATCH] dsa: tag_rtl4_a: Bump min packet size Linus Walleij
2023-10-27 21:23 ` Florian Fainelli
2023-10-27 23:03 ` Andrew Lunn
2023-10-29 22:18 ` David Laight
2023-10-29 15:38 ` Linus Walleij
2023-10-29 17:35 ` Andrew Lunn [this message]
2023-10-30 12:51 ` Vladimir Oltean
2023-10-30 14:29 ` Linus Walleij
2023-10-30 14:32 ` Linus Walleij
2023-10-28 22:04 ` Vladimir Oltean
2023-10-29 22:15 ` Linus Walleij
2023-10-29 23:00 ` Andrew Lunn
2023-10-30 7:39 ` Linus Walleij
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=6c10edf1-dad1-4a4f-ae0e-42b17febbd5d@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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