On 8/16/2016 8:26 AM, Yuanhan Liu wrote: > On Tue, Aug 09, 2016 at 04:42:33PM +0530, Pankaj Chauhan wrote: >> >> Hi, >> >> I am working on an NXP platform where we intend to use user space vhost >> switch (examples/vhost) as backend for VIRTIO devices. But there are two >> limitations in current vhost-switch (examples/vhost)that are restricting my >> use case: >> >> 1. The vhost-switch application is tightly integrated with Intel VMDQ. Since >> my device doesn't have VMDQ i can not use this application directly. > > Sorry being late (I was on biz trip last week). > > Yes, a vhost example should not do that. We have an internal TODO to > remove it. Actually, to make it optional, and Jianfeng was working on > that. Well, seems that you two have already had some discussions.
Yes I had a discussion with Jianfeng and he has sent the work items on the list. > >> 2. The vhost-switch application supports only one external or physical port >> (non virtio devices), but my requirement is to have multiple physical ports >> and multiple virtio devices. > > What are you going to achieve? BTW, have you tried testpmd (with vhost-pmd)? > I'm with impression that it might be a better option to you. > > --yliu My use case is that my machine/board which is not sitting as end node of network but somewhere in between like an router. So the traffic looks something like this: Physical port 1 -> Enter VM(s) through virtio -> exit from physical port 2 For above use case i need a vhost-back-end which supports multiple physical ports. Thanks for the suggestion of vhost-pmd ( i was not aware of that), i'll explore possibility of using it for my use case of multiple physical ports. thanks, Pankaj >
