[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240415102659.7f72ae8d@kernel.org>
Date: Mon, 15 Apr 2024 10:26:59 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org, pabeni@...hat.com, davem@...emloft.net,
edumazet@...gle.com, parav@...dia.com, mst@...hat.com, jasowang@...hat.com,
xuanzhuo@...ux.alibaba.com, shuah@...nel.org, petrm@...dia.com,
liuhangbin@...il.com, vladimir.oltean@....com, bpoirier@...dia.com,
idosch@...dia.com, virtualization@...ts.linux.dev
Subject: Re: [patch net-next 0/6] selftests: virtio_net: introduce initial
testing infrastructure
On Sat, 13 Apr 2024 15:23:53 +0200 Jiri Pirko wrote:
> That is a goal. Currently I do it with:
> vng --qemu-opts="-nic tap,id=nd0,ifname=xtap0,model=virtio-net-pci,script=no,downscript=no,mac=52:54:00:12:34:57 -nic tap,id=nd1,ifname=xtap1,model=virtio-net-pci,script=no,downscript=no,mac=52:54:00:12:34:58"
>
> and setting loop manually with tc-matchall-mirred
>
> Implementing virtio loop instantiation in vng is on the todo list for
> this.
Just to be clear - I think the loop configuration is better off outside
vng. It may need SUID and such. We just need to make vng spawn the two
interfaces with a less verbose syntax. --network-count 2 ?
Powered by blists - more mailing lists