Date: Mon, 20 Mar 2017 12:50:40 +0100 From: Vincenzo Maffione <v.maffione@gmail.com> To: Harry Schmalzbauer <freebsd@omnilan.de> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Are ./valte-ctl and ./bridge friends or competitors? Message-ID: <CA%2B_eA9hso4AKpFEJCXWHYYz5tbLx4jT2o=3c-3YrWM98ovB8%2BA@mail.gmail.com> In-Reply-To: <58CFA606.7090306@omnilan.de> References: <58CBA727.3040108@omnilan.de> <58CBBF7A.8050604@omnilan.de> <CA%2B_eA9jYxRoi2HPcVjKbifTM43nnHeMQGDmmQvsw5UdXtLmFug@mail.gmail.com> <58CC26CF.5050708@omnilan.de> <CA%2B_eA9j30Shp1QB%2B6UY1YRqsWKRo4xqPvDRnMHT25VQL4QhQ_Q@mail.gmail.com> <58CFA606.7090306@omnilan.de>
next in thread | previous in thread | raw e-mail | index | archive | help
2017-03-20 10:51 GMT+01:00 Harry Schmalzbauer <freebsd@omnilan.de>: > Bez=C3=BCglich Vincenzo Maffione's Nachricht vom 18.03.2017 09:29 (localt= ime): > >=E2=80=A6 > >>> Actually, there is pending work on bhyve and netmap, that is going to > be > >>> merged soon, available at https://github.com/vmaffione/freebsd/ in > >>> branch ptnet-head. > >>> > >>> If you are interested, here there is some information > >>> https://wiki.freebsd.org/DevSummit/201609?action=3D > >> AttachFile&do=3Dview&target=3D20160923-freebsd-summit-ptnet.pdf > >>> <https://wiki.freebsd.org/DevSummit/201609?action=3D > >> AttachFile&do=3Dview&target=3D20160923-freebsd-summit-ptnet.pdf> > >>> together with bhyve cmdlines. > > Congratulations, nice work and presentation :-) > Thanks! > > =E2=80=A6 > >> So I'm a bit lost regarding furhter decisions. My prefered if_lagg(4) > >> setup doesn't work with netmap at the moment, if_bridge(4) has > >> in-house-overhead and forces me to either drop jumbo frames completely > >> or use 9k MTU for any bridge member. > >> Will look into openvSwitch. Or better get some card providing VFs? > >> Or wait the ptnet merge and check if I can deploy my desired setup the= n? > >> And, I want to keep TSO and HWVLAN_TAG on the host interfaces=E2=80=A6 > >> > >> > > It depends on your requirements, in terms of connectivity between VMs a= nd > > NICs and required performance (for a given workload, e.g. average > > packet-size, average packet rate, etc.). > > If you really want TSO an other offloadings on the phyisical NIC, then > you > > cannot use that NIC in netmap mode (e.g. attaching it to VALE). > > So to summarize for newbies exploring netmap(4) world in combination > with physical uplinks and virtual interfaces, it's important to do the > following uplink NIC configuration (ifconfig(8)): > -rxcsum -txcsum -rxcsum6 -txcsum6 -tso -lro promisc > Exactly. This is mentioned at the very end of netmap(4): "netmap does not use features such as checksum offloading, TCP segmentation offloading, encryption, VLAN encapsulation/decapsulation, etc. When using netmap to exchange packets with the host stack, make sure to disable these features." But it is probably a good idea to add these example ifconfig instructions somewhere (man page or at least the README in the netmap repo). > > I guess vlanhwtag, vlanhwfilter and vlanhwtso don't interfere, do they? > Well, I think they interfere: if you receive a tagged packet and the NIC strips the tag and puts it in the packet descriptor, then with netmap you will see the untagged packet, and you wouldn't have a way to see the tag. Cheers, Vincenzo > > Thanks, > > -harry > --=20 Vincenzo Maffione
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B_eA9hso4AKpFEJCXWHYYz5tbLx4jT2o=3c-3YrWM98ovB8%2BA>