On Tue, Oct 20, 2015 at 06:16:23AM +0000, Xie, Huawei wrote:
> On 10/9/2015 1:46 PM, Yuanhan Liu wrote:
> > From: Changchun Ouyang <changchun.ouyang at intel.com>
> >
> > The new API rte_vhost_core_id_set() is to bind a virtq to a specific
> > core, while the another API rte_vhost_core_id_get() is for getting
> > the bind core for a virtq.
> Where is the absolute necessity to put switching/application logic into
> vhost virt queue structure?
I don't think it's a must, and we can drop it.
> Besides, suggest seperate vhost example patchset and vhost library
> patchset so that if we have issue with one, it doesn't stop another
> being merged.
That's what I've done: patch 1-8 are for enabling vhost-user mq, while
other patches are for vhost-switch example. Maybe I should send out 2
patch sets, one for each.
But, anyway, please help focus on reviewing path 1-8.
--yliu
> >
> > The usage, which will be introduced soon, could be find at
> > examles/vhost/main.c.
> >
> > Signed-off-by: Changchun Ouyang <changchun.ouyang at intel.com>
> > Signed-off-by: Yuanhan Liu <yuanhan.liu at linux.intel.com>
> > ---
>
