search for: eswitch

Hi List, Would someone can to explain me the main difference in SWITCHES or ESWITCHES in AEL. context default { switches { DUNDi/e164; IAX2/box5; }; eswitches { IAX2/context@${CURSERVER}; }; }; All the best, Thiago -- ---------------------------------------------------------------- Thiago Maluf Resende Tel: +55 21 9700-9113 e-mail: ma...

...to all mlx5 devices net/mlx5: Register mlx5 devices to auxiliary virtual bus vdpa/mlx5: Connect mlx5_vdpa to auxiliary bus net/mlx5e: Connect ethernet part to auxiliary bus RDMA/mlx5: Convert mlx5_ib to use auxiliary bus net/mlx5: Delete custom device management logic net/mlx5: Simplify eswitch mode check RDMA/mlx5: Remove IB representors dead code drivers/infiniband/hw/mlx5/counters.c | 7 - drivers/infiniband/hw/mlx5/ib_rep.c | 113 ++-- drivers/infiniband/hw/mlx5/ib_rep.h | 45 +- drivers/infiniband/hw/mlx5/main.c | 148 +++-- drivers/infi...

...ranch 'mlx5-next' of git://git.kernel.org/.../mellanox/linux into HEAD virtio_config: fix up warnings on parisc vdpa_sim: init iommu lock vdpa/mlx5: fix up endian-ness for mtu Parav Pandit (2): net/mlx5: Avoid RDMA file inclusion in core driver net/mlx5: Avoid eswitch header inclusion in fs core layer Tariq Toukan (1): net/mlx5: kTLS, Improve TLS params layout structures Zhu Lingshan (7): vhost: introduce vhost_vring_call kvm: detect assigned device via irqbypass manager vDPA: add get_vq_irq() in vdpa_config_ops vhost_vdpa: implem...

...server/local ; ; An "lswitch" is like a switch but is literal, in that ; variable substitution is not performed at load time ; but is passed to the switch directly (presumably to ; be substituted in the switch routine itself) ; ; lswitch => Loopback/12${EXTEN}@othercontext ; ; An "eswitch" is like a switch but the evaluation of ; variable substitution is performed at runtime before ; being passed to the switch routine. ; ; eswitch => IAX2/context@${CURSERVER} [macro-stdexten]; ; ; Standard extension macro: ; ${ARG1} - Extension (we could have used ${MACRO_EXTEN} here as...

...ial(SIP/cgm); 102 => Dial(SIP/bluecommand); _9XX => ?????????? 500 => Agi(agi://localhost/internal.agi); _8XXX => { NoOp("Calling ${EXTEN}"); Dial(SIP/${EXTEN}); } }; context database { eswitches { Realtime/ContextShouldBeHere@${CURSERVER}; }; } I want it to jump from _9XX to the context database, passing along what context it came from as a parameter. Is this possible at all? Greetings, Christian

...to what the original > virtio_net was. That makes sense. Is it udev/naming that you're most concerned about here? I.e. what's the user space app that expects the netdev to be linked? This is just out of curiosity, the linking of netdevs to devices is a bit of a PITA in the switchdev eswitch mode world, with libvirt expecting only certain devices to be there.. Right now we're not linking VF reprs, which breaks naming. I wanted to revisit that. > > FWIW two solutions that immediately come to mind is to export "backup" > > as phys_port_name of the backup virt...

Hi all, I've put up a blog post with a summary of where network device failover stands and some open issues. Not sure where best to host it, I just put it up on blogspot: https://mstsirkin.blogspot.com/2019/03/virtio-network-device-failover-support.html Comments, corrections are welcome! -- MST

Hi all, I've put up a blog post with a summary of where network device failover stands and some open issues. Not sure where best to host it, I just put it up on blogspot: https://mstsirkin.blogspot.com/2019/03/virtio-network-device-failover-support.html Comments, corrections are welcome! -- MST

...to avoid DHCP on net-failover slaves? (Not sure. Asking...) 4) Another interesting use-case where the net-failover mechanism is useful is for handling NIC firmware failures or NIC firmware Live-Upgrade. In both cases, there is a need to perform a full PCIe reset of the NIC. Which lose all the NIC eSwitch configuration of the various VFs. To handle these cases gracefully, one could just hot-unplug all VFs from guests running on host (which will make all guests now use the virtio-net netdev which is backed by a netdev that eventually is on top of PF). Therefore, networking will be restored to guests...

...on net-failover slaves? (Not sure. Asking...) > > 4) Another interesting use-case where the net-failover mechanism is useful is for handling NIC firmware failures or NIC firmware Live-Upgrade. > In both cases, there is a need to perform a full PCIe reset of the NIC. Which lose all the NIC eSwitch configuration of the various VFs. In this setup, how does VF keep going? If it doesn't keep going, why is it helpful? > To handle these cases gracefully, one could just hot-unplug all VFs from guests running on host (which will make all guests now use the virtio-net netdev which is backed...

On Fri, Feb 16, 2018 at 6:38 PM, Jakub Kicinski <kubakici at wp.pl> wrote: > On Fri, 16 Feb 2018 10:11:19 -0800, Sridhar Samudrala wrote: >> Ppatch 2 is in response to the community request for a 3 netdev >> solution. However, it creates some issues we'll get into in a moment. >> It extends virtio_net to use alternate datapath when available and >> registered.

On Fri, Feb 16, 2018 at 6:38 PM, Jakub Kicinski <kubakici at wp.pl> wrote: > On Fri, 16 Feb 2018 10:11:19 -0800, Sridhar Samudrala wrote: >> Ppatch 2 is in response to the community request for a 3 netdev >> solution. However, it creates some issues we'll get into in a moment. >> It extends virtio_net to use alternate datapath when available and >> registered.