Re: Is network backend vde worth keeping? (was: Is network backend netmap worth keeping?)

On 09/10/2019 11.13, Thomas Huth wrote: > On 07/10/2019 20.21, Markus Armbruster wrote: >> Markus Armbruster writes: >> >>> Please excuse the attention-grabbing subject. >> >> Again. >> >> [...] >>> So, to make use of QEMU's netmap backend (CONFIG_NETMAP), you have to >>> build and install netmap

Re: Is network backend vde worth keeping? (was: Is network backend netmap worth keeping?)

On Mon, Oct 07, 2019 at 08:21:14PM +0200, Markus Armbruster wrote: > Markus Armbruster writes: > > > Please excuse the attention-grabbing subject. > > Again. > > [...] > > So, to make use of QEMU's netmap backend (CONFIG_NETMAP), you have to > > build and install netmap software from sources.

Re: Is network backend vde worth keeping? (was: Is network backend netmap worth keeping?)

On Mon, Oct 7, 2019 at 8:23 PM Markus Armbruster wrote: > > Markus Armbruster writes: > > > Please excuse the attention-grabbing subject. > > Again. > > [...] > > So, to make use of QEMU's netmap backend (CONFIG_NETMAP), you have to > > build and install netmap software from sources. Which

Re: Is network backend vde worth keeping? (was: Is network backend netmap worth keeping?)

On 07/10/2019 20.21, Markus Armbruster wrote: > Markus Armbruster writes: > >> Please excuse the attention-grabbing subject. > > Again. > > [...] >> So, to make use of QEMU's netmap backend (CONFIG_NETMAP), you have to >> build and install netmap software from sources. Which pretty much > >

Is network backend vde worth keeping? (was: Is network backend netmap worth keeping?)

Markus Armbruster writes: > Please excuse the attention-grabbing subject. Again. [...] > So, to make use of QEMU's netmap backend (CONFIG_NETMAP), you have to > build and install netmap software from sources. Which pretty much CONFIG_VDE seems to be similarly cumbersome to build-test. >