mbox series

[net-next,0/5] net: dsa: loop: Preparatory changes for

Message ID 20200803200354.45062-1-f.fainelli@gmail.com
Headers show
Series net: dsa: loop: Preparatory changes for | expand

Message

Florian Fainelli Aug. 3, 2020, 8:03 p.m. UTC 
Hi David,

These patches are all meant to help pave the way for a 802.1Q data path
added to the mockup driver, making it more useful than just testing for
configuration. Sending those out now since there is no real need to
wait.

Thanks

Florian Fainelli (5):
  net: dsa: loop: PVID should be per-port
  net: dsa: loop: Support 4K VLANs
  net: dsa: loop: Move data structures to header
  net: dsa: loop: Wire-up MTU callbacks
  net: dsa: loop: Set correct number of ports

 drivers/net/dsa/dsa_loop.c | 61 ++++++++++++++------------------------
 include/linux/dsa/loop.h   | 41 +++++++++++++++++++++++++
 2 files changed, 64 insertions(+), 38 deletions(-)
 create mode 100644 include/linux/dsa/loop.h

Comments

Andrew Lunn Aug. 3, 2020, 8:33 p.m. UTC | #1 
On Mon, Aug 03, 2020 at 01:03:49PM -0700, Florian Fainelli wrote:
> Hi David,
> 
> These patches are all meant to help pave the way for a 802.1Q data path
> added to the mockup driver, making it more useful than just testing for
> configuration.

Could you give some more details. I assume the tag driver is going be
to more active. At least, that would make sense with the data
structure moves.

	  Andrew
Florian Fainelli Aug. 3, 2020, 8:36 p.m. UTC | #2 
On 8/3/2020 1:33 PM, Andrew Lunn wrote:
> On Mon, Aug 03, 2020 at 01:03:49PM -0700, Florian Fainelli wrote:
>> Hi David,
>>
>> These patches are all meant to help pave the way for a 802.1Q data path
>> added to the mockup driver, making it more useful than just testing for
>> configuration.
> 
> Could you give some more details. I assume the tag driver is going be
> to more active. At least, that would make sense with the data
> structure moves.

Still working on a 802.1Q data path that allows to carry VLAN tags from
the DSA CPU interface (guest side) to a tap (host side) and from there
you can ping, bridge etc. devices. I am having some problems with the
responses sent back to the guest which are incorrectly tagged on ingress.

You can see the WIP here:
https://github.com/ffainelli/linux/commits/dsa-loop-8021q
David Miller Aug. 4, 2020, 1:20 a.m. UTC | #3 
From: Florian Fainelli <f.fainelli@gmail.com>
Date: Mon,  3 Aug 2020 13:03:49 -0700

> These patches are all meant to help pave the way for a 802.1Q data path
> added to the mockup driver, making it more useful than just testing for
> configuration. Sending those out now since there is no real need to
> wait.

Series applied, I added "a 802.1Q data path" to the subject line I integrated
into the merge commit for the series as it seems your Subject line here was
chopped off.
Florian Fainelli Aug. 4, 2020, 2:22 a.m. UTC | #4 
On 8/3/2020 6:20 PM, David Miller wrote:
> From: Florian Fainelli <f.fainelli@gmail.com>
> Date: Mon,  3 Aug 2020 13:03:49 -0700
> 
>> These patches are all meant to help pave the way for a 802.1Q data path
>> added to the mockup driver, making it more useful than just testing for
>> configuration. Sending those out now since there is no real need to
>> wait.
> 
> Series applied, I added "a 802.1Q data path" to the subject line I integrated
> into the merge commit for the series as it seems your Subject line here was
> chopped off.

Yes it was, the merge commit looks good to me, thank you.