DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Benoît Canet" <benoit.canet@irqsave.net>
To: "Xie, Huawei" <huawei.xie@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] vhost user examples
Date: Tue, 27 Jan 2015 18:15:32 +0100	[thread overview]
Message-ID: <20150127171532.GD21462@irqsave.net> (raw)
In-Reply-To: <C37D651A908B024F974696C65296B57B0F362CC1@SHSMSX101.ccr.corp.intel.com>

The Tuesday 27 Jan 2015 à 17:10:29 (+0000), Xie, Huawei wrote :
> 
> 
> > -----Original Message-----
> > From: Benoît Canet [mailto:benoit.canet@irqsave.net]
> > Sent: Wednesday, January 28, 2015 1:00 AM
> > To: Xie, Huawei
> > Cc: Benoît Canet; dev@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@irqsave.net]
> > > > Sent: Tuesday, January 27, 2015 10:11 PM
> > > > To: Xie, Huawei; dev@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.

Thanks a lot

I am looking forward receiving my intel network card and testing
it.

Best regards

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

      reply	other threads:[~2015-01-27 17:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 14:11 Benoît Canet
2015-01-27 16:33 ` Xie, Huawei
2015-01-27 16:59   ` Benoît Canet
2015-01-27 17:10     ` Xie, Huawei
2015-01-27 17:15       ` Benoît Canet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150127171532.GD21462@irqsave.net \
    --to=benoit.canet@irqsave.net \
    --cc=dev@dpdk.org \
    --cc=huawei.xie@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).