[dpdk-dev] vhost user examples

Xie, Huawei huawei.xie at intel.com
Tue Jan 27 18:10:29 CET 2015



> -----Original Message-----
> From: Benoît Canet [mailto:benoit.canet at irqsave.net]
> Sent: Wednesday, January 28, 2015 1:00 AM
> To: Xie, Huawei
> Cc: Benoît Canet; dev at dpdk.org
> Subject: Re: vhost user examples
> 
> The Tuesday 27 Jan 2015 à 16:33:19 (+0000), Xie, Huawei wrote :
> >
> > > -----Original Message-----
> > > From: Benoît Canet [mailto:benoit.canet at irqsave.net]
> > > Sent: Tuesday, January 27, 2015 10:11 PM
> > > To: Xie, Huawei; dev at dpdk.org
> > > Subject: vhost user examples
> > >
> > >
> > > Hi Xie,
> > >
> > > I would be interested in alpha testing the vhost user patchset.
> > >
> > > Is there an up to date example of how to use it ?
> > >
> >
> > vHost has a parameter called base_name. Temporarily you could specify --
> base-name as
> > the unix domain socket path, and set it in the qemu command line as socket
> path.
> > recommended qemu command line for memory and vhost configuration:
> > -m $MEM -object memory-backend-file,id=mem,size=${MEM}M,mem-
> path=/mnt/huge,share=on -numa node,memdev=mem  -mem-prealloc
> > -chardev socket,id=char0,path=$sock_path  -netdev type=vhost-
> user,id=mynet1,chardev=char0,vhostforce \
> > -device virtio-net-pci,mac=52:54:00:12:34:11,netdev=mynet1
> 
> Thanks,
> 
> Is the upstream vhost example in master already patched for this ?
> Or does it still required some patches ?
Yes, vhost example already supports base_name parameter.
Previously it is used for name of the vhost character device file.
You could use it as socket path name.

> 
> Best regards
> 
> Benoît
> 
> >
> > > Best regards
> > >
> > > Benoît


More information about the dev mailing list