Displaying 20 results from an estimated 353 matches for "dpdk".
2017 Jul 20
0
OVS+DPDK Problem
Hi All,
First time mailing here.
I have installed on a CentOS 7.0 KVM (with DPDK and OVS) one Deep Packet
Inspection VM.
I have one channel and some virtual traffic generator.
The traffic is lost between dpdk vhostuser and the DPI VM.
The setup is attached. Any suggestions or ideas?
Regarding the OVS+DPDK configuration, the following configuration is
already made:
- SELINUX is...
2019 Mar 28
1
Error Starting domain: Failed to page size of file
I am trying to connect a KVM-QEMU VM to OVS-DPDK vhostuser port. But, I am
encountering a few errors. Since I am very new to libvrt and Linux I am not
able to sort them out. Any guidance in this regard would be a great help.
These are my System Logs:
Mar 28 18:03:04 dpdk-OptiPlex-5040 libvirtd.service: 1529: debug :
virCommandRunAsync:2429 : Ab...
2018 Apr 23
5
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...common code for netvsc especially the
>> > > > >three device model. MS worked hard with distro vendors to support transparent
>> > > > >mode, ans we really can't have a new model; or do backport.
>> > > > >
>> > > > >Plus, DPDK is now dependent on existing model.
>> > > >
>> > > > Sorry, but nobody here cares about dpdk or other similar oddities.
>> > >
>> > > The network device model is a userspace API, and DPDK is a userspace application.
>> >
>> >...
2018 Apr 23
5
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...common code for netvsc especially the
>> > > > >three device model. MS worked hard with distro vendors to support transparent
>> > > > >mode, ans we really can't have a new model; or do backport.
>> > > > >
>> > > > >Plus, DPDK is now dependent on existing model.
>> > > >
>> > > > Sorry, but nobody here cares about dpdk or other similar oddities.
>> > >
>> > > The network device model is a userspace API, and DPDK is a userspace application.
>> >
>> >...
2018 Apr 23
2
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...>I will NAK patches to change to common code for netvsc especially the
> > > >three device model. MS worked hard with distro vendors to support transparent
> > > >mode, ans we really can't have a new model; or do backport.
> > > >
> > > >Plus, DPDK is now dependent on existing model.
> > >
> > > Sorry, but nobody here cares about dpdk or other similar oddities.
> >
> > The network device model is a userspace API, and DPDK is a userspace application.
>
> It is userspace but are you sure dpdk is ac...
2018 Apr 23
2
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...>I will NAK patches to change to common code for netvsc especially the
> > > >three device model. MS worked hard with distro vendors to support transparent
> > > >mode, ans we really can't have a new model; or do backport.
> > > >
> > > >Plus, DPDK is now dependent on existing model.
> > >
> > > Sorry, but nobody here cares about dpdk or other similar oddities.
> >
> > The network device model is a userspace API, and DPDK is a userspace application.
>
> It is userspace but are you sure dpdk is ac...
2018 Apr 23
3
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...el is wrong.
>
>
> >
> >I will NAK patches to change to common code for netvsc especially the
> >three device model. MS worked hard with distro vendors to support transparent
> >mode, ans we really can't have a new model; or do backport.
> >
> >Plus, DPDK is now dependent on existing model.
>
> Sorry, but nobody here cares about dpdk or other similar oddities.
The network device model is a userspace API, and DPDK is a userspace application.
You can't go breaking userspace even if you don't like the application.
2018 Apr 23
3
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...el is wrong.
>
>
> >
> >I will NAK patches to change to common code for netvsc especially the
> >three device model. MS worked hard with distro vendors to support transparent
> >mode, ans we really can't have a new model; or do backport.
> >
> >Plus, DPDK is now dependent on existing model.
>
> Sorry, but nobody here cares about dpdk or other similar oddities.
The network device model is a userspace API, and DPDK is a userspace application.
You can't go breaking userspace even if you don't like the application.
2018 Apr 24
1
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...t; > >> > > > >three device model. MS worked hard with distro vendors to support transparent
> > >> > > > >mode, ans we really can't have a new model; or do backport.
> > >> > > > >
> > >> > > > >Plus, DPDK is now dependent on existing model.
> > >> > > >
> > >> > > > Sorry, but nobody here cares about dpdk or other similar oddities.
> > >> > >
> > >> > > The network device model is a userspace API, and DPDK is a userspa...
2016 Apr 18
1
Potential hang in virtnet_send_command
Hi,
I was debugging an issue caused by a bad usage of dpdk.
That is fixed in the meantime and I'll backport that into our code as well.
But along debugging that, I found a potential hang in virtnet_send_command
that my case ran into.
The following code can become an infinite loop:
/* Spin for a response, the kick causes an ioport write, trapping
* in...
2016 Apr 18
1
Potential hang in virtnet_send_command
Hi,
I was debugging an issue caused by a bad usage of dpdk.
That is fixed in the meantime and I'll backport that into our code as well.
But along debugging that, I found a potential hang in virtnet_send_command
that my case ran into.
The following code can become an infinite loop:
/* Spin for a response, the kick causes an ioport write, trapping
* in...
2018 Feb 22
3
"scripts are not supported on interfaces of type vhostuser" error
Hi,
I'm having trouble starting a VM with vhostuser interfaces.
I have a simple configuration where a VM running Debian has 1 vhostuser
interface plugged into an OVS switch where a DPDK interface is already
plugged in.
$ ovs-vsctl show:
Bridge "switch1"
Port "switch1"
Interface "switch1"
type: internal
Port "1.switch1"
Interface "1.switch1"
type: dpdk
options: {dpdk-devarg...
2018 Apr 25
2
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...e
>> >> > > > >three device model. MS worked hard with distro vendors to support transparent
>> >> > > > >mode, ans we really can't have a new model; or do backport.
>> >> > > > >
>> >> > > > >Plus, DPDK is now dependent on existing model.
>> >> > > >
>> >> > > > Sorry, but nobody here cares about dpdk or other similar oddities.
>> >> > >
>> >> > > The network device model is a userspace API, and DPDK is a userspace appli...
2018 Apr 25
2
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...e
>> >> > > > >three device model. MS worked hard with distro vendors to support transparent
>> >> > > > >mode, ans we really can't have a new model; or do backport.
>> >> > > > >
>> >> > > > >Plus, DPDK is now dependent on existing model.
>> >> > > >
>> >> > > > Sorry, but nobody here cares about dpdk or other similar oddities.
>> >> > >
>> >> > > The network device model is a userspace API, and DPDK is a userspace appli...
2015 Sep 17
0
[dpdk-dev] virtio optimization idea
...avail ring in the virtio processing
>>> core. When vhost processes the avail ring, the cache line transfer from
>>> virtio processing core to vhost processing core takes pretty much CPU
>>> cycles.
>>> To solve this problem, this is the arrangement of RX ring for DPDK
>>> pmd(for non-mergable case).
>>>
>>> avail
>>> idx
>>> +
>>> |...
2015 Sep 17
0
[dpdk-dev] virtio optimization idea
...avail ring in the virtio processing
>>> core. When vhost processes the avail ring, the cache line transfer from
>>> virtio processing core to vhost processing core takes pretty much CPU
>>> cycles.
>>> To solve this problem, this is the arrangement of RX ring for DPDK
>>> pmd(for non-mergable case).
>>>
>>> avail
>>> idx
>>> +
>>> |...
2015 Apr 09
1
[dpdk-dev] [snabb-devel] Re: memory barriers in virtq.lua?
Howdy,
On 8 April 2015 at 17:15, Xie, Huawei <huawei.xie at intel.com> wrote:
> luke:
> 1. host read the flag. 2 guest toggles the flag 3.guest checks the used.
> 4. host update used.
> Is this your case?
>
Yep, that is exactly the case I mean.
Cheers,
-Luke
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2018 Apr 23
0
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...es to change to common code for netvsc especially the
> > > > >three device model. MS worked hard with distro vendors to support transparent
> > > > >mode, ans we really can't have a new model; or do backport.
> > > > >
> > > > >Plus, DPDK is now dependent on existing model.
> > > >
> > > > Sorry, but nobody here cares about dpdk or other similar oddities.
> > >
> > > The network device model is a userspace API, and DPDK is a userspace application.
> >
> > It is userspa...
2015 Apr 09
1
[dpdk-dev] [snabb-devel] Re: memory barriers in virtq.lua?
Howdy,
On 8 April 2015 at 17:15, Xie, Huawei <huawei.xie at intel.com> wrote:
> luke:
> 1. host read the flag. 2 guest toggles the flag 3.guest checks the used.
> 4. host update used.
> Is this your case?
>
Yep, that is exactly the case I mean.
Cheers,
-Luke
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2018 Apr 24
0
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...sc especially the
> >> > > > >three device model. MS worked hard with distro vendors to support transparent
> >> > > > >mode, ans we really can't have a new model; or do backport.
> >> > > > >
> >> > > > >Plus, DPDK is now dependent on existing model.
> >> > > >
> >> > > > Sorry, but nobody here cares about dpdk or other similar oddities.
> >> > >
> >> > > The network device model is a userspace API, and DPDK is a userspace application.
&g...