On 8/24/2016 12:58 PM, Maxime Coquelin wrote:
>
>
> On 08/18/2016 04:35 AM, Tan, Jianfeng wrote:
>> Hi Maxime,
>>
>> On 8/17/2016 7:18 PM, Maxime Coquelin wrote:
>>> Hi Jianfeng,
>>>
>>> On 08/17/2016 04:33 AM, Tan, Jianfeng wrote:
Hi,
Please review below proposal of Pankaj and mysel
On 08/18/2016 04:35 AM, Tan, Jianfeng wrote:
> Hi Maxime,
>
> On 8/17/2016 7:18 PM, Maxime Coquelin wrote:
>> Hi Jianfeng,
>>
>> On 08/17/2016 04:33 AM, Tan, Jianfeng wrote:
>>> Hi,
>>>
>>> Please review below proposal of Pankaj and myself after an offline
>>> discussion. (Pankaj, please correct
2016-08-18 10:36, Tan, Jianfeng:
> From: Maxime Coquelin [mailto:maxime.coquelin at redhat.com]
> > > On 8/17/2016 7:18 PM, Maxime Coquelin wrote:
> > >> On 08/17/2016 04:33 AM, Tan, Jianfeng wrote:
> > >>> b. Abstract switching logic into a framework, so that we can develop
> > >>> different kind
On Wed, Aug 17, 2016 at 03:54:21PM +0530, Pankaj Chauhan wrote:
> 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 p
ect: Re: [dpdk-dev] vhost [query] : support for multiple ports and non
> VMDQ devices in vhost switch
>
> Hi,
>
> On 08/18/2016 04:35 AM, Tan, Jianfeng wrote:
> > Hi Maxime,
> >
> > On 8/17/2016 7:18 PM, Maxime Coquelin wrote:
> >> Hi Jianfeng,
>
Hi Maxime,
On 8/17/2016 7:18 PM, Maxime Coquelin wrote:
> Hi Jianfeng,
>
> On 08/17/2016 04:33 AM, Tan, Jianfeng wrote:
>> Hi,
>>
>> Please review below proposal of Pankaj and myself after an offline
>> discussion. (Pankaj, please correct me if I'm going somewhere wrong).
>>
>> a. Remove HW depend
Hi,
On 08/18/2016 04:35 AM, Tan, Jianfeng wrote:
> Hi Maxime,
>
> On 8/17/2016 7:18 PM, Maxime Coquelin wrote:
>> Hi Jianfeng,
>>
>> On 08/17/2016 04:33 AM, Tan, Jianfeng wrote:
>>> Hi,
>>>
>>> Please review below proposal of Pankaj and myself after an offline
>>> discussion. (Pankaj, please corre
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 vh
Hi Jianfeng,
On 08/17/2016 04:33 AM, Tan, Jianfeng wrote:
> Hi,
>
> Please review below proposal of Pankaj and myself after an offline
> discussion. (Pankaj, please correct me if I'm going somewhere wrong).
>
> a. Remove HW dependent option, --strip-vlan, because different kinds of
> NICs behave d
Hi,
Please review below proposal of Pankaj and myself after an offline
discussion. (Pankaj, please correct me if I'm going somewhere wrong).
a. Remove HW dependent option, --strip-vlan, because different kinds of
NICs behave differently. It's a bug fix.
b. Abstract switching logic into a framew
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
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
12 matches
Mail list logo
