I don't think 8-10 S-VLANs with 4K C-VLANs totaling ~40K sub-interfaces will be 
an issue for VPP to handle, as long as the NICs being polled by device-input 
node from DPDK or other device drivers are not at a large scale.



I am not clear what was done with PPPoE to address similar issues. I suppose 
VPP can in theory be enhanced to support IP forwarding on "inner dot1q any" 
sub-interfaces as follows:

  *   All ARP entries for output IP addresses on that sub-interface must be 
statically provisioned by control plane via API or user CLI. This means the set 
IP ARP CLI/API needs to be enhanced to specify what are the inner VLAN tag to 
use for ARP entry.
  *   The handling of glean adjacency for any IP address using this 
sub-interface without ARP entry should probably be changed to not sent any ARP 
requests.
  *   We also need to enhance VPP's arp-request handling on that sub-interface 
so the VLAN tags are preserved on arp-response.  Or alternatively, require any 
neighbor of the sub-interface to have ARP entries provisioned so it won’t sent 
ARP requests.



I am not sure how much work will be involved in doing this, or if there is any 
other changes I may have missed.



Regards,

John



-----Original Message-----

From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Raj

Sent: Wednesday, December 18, 2019 8:32 AM

To: vpp-dev <vpp-dev@lists.fd.io>

Subject: Re: [vpp-dev] QinQ and dot1ad any



On Tue, Dec 17, 2019 at 7:43 PM John Lo (loj) <l...@cisco.com> wrote:



> Without exact match on a L3 sub-interface, VPP has no mechanism to

> know what VLAN tags to use for packet output, such as ARP request packets or 
> IP packets, on that sub-interface.



For a big QinQ network (like say about 8 - 10 S-VLAN each with 4K

C-VLANs) , the number of interface can become huge. Will that hit some internal 
VPP limits or will it become a performance problem?



Is it a good idea to have a mechanism to provide this information to VPP via a 
control plane application, like whats is being done for PPPoE, so that only 
outer VLAN interface needs to be created, while inner VLAN interface will be 
provided by the control plane application? Is this a road worth traveling?



Thanks and Regards,



Raj
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14923): https://lists.fd.io/g/vpp-dev/message/14923
Mute This Topic: https://lists.fd.io/mt/68757125/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to