[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d8ab871-1d0e-4f6d-70d0-0d8d6dc9d4d2@gmail.com>
Date: Mon, 3 Aug 2020 13:36:53 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, Vivien Didelot <vivien.didelot@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>
Subject: Re: [PATCH net-next 0/5] net: dsa: loop: Preparatory changes for
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
--
Florian
Powered by blists - more mailing lists