2017-01-12 6:18 GMT-08:00 Binbin Xu :
> We can hotplug attach DPDK ports specified via the 'dpdk-devargs'
> option now.
>
> But the socket id of DPDK ports can't be assigned correctly,
> it is always 0. The socket id of DPDK ports should be assigned
> according to the numa
We can hotplug attach DPDK ports specified via the 'dpdk-devargs'
option now.
But the socket id of DPDK ports can't be assigned correctly,
it is always 0. The socket id of DPDK ports should be assigned
according to the numa id of the device.
Fixes: 55e075e65ef9e ("netdev-dpdk: Arbitrary 'dpdk'
Thank you for your suggestion, i will reformat the message and resubmit
the patch ASAP.
Aaron Conole 写于 2017/01/11 22:27:06:
> 发件人: Aaron Conole
> 收件人: Binbin Xu ,
> 抄送: d...@openvswitch.org, Ciara Loftus
[ View in browser ]( http://r.newsletter.bonescamail.nl/nru6qvdqoatrf.html
)
[ ]( http://r.newsletter.bonescamail.nl/2n3cqzhilaoatrd.html )
SPECIAL OFFER CANNED SARDINES IN OIL
Scientific Name: Sardina Piclhardus
Packing: 25 x 125 gr
Origin: Marocco
Expiry: 31-03-2019
PRICE
Looks good to me:
Acked-by: Jarno Rajahalme
> On Jan 11, 2017, at 3:37 PM, Andy Zhou wrote:
>
> The may_steal flag is now used, Remove OVS_UNUSED.
>
> Since dp_packet_delete() handles the NULL pointer properly, we can
> drop a few tracking variables, and make
> On Jan 11, 2017, at 12:10 AM, Jan Scheurich wrote:
>
>
> On 2017-01-11 01:14, Jarno Rajahalme wrote:
>>
>> Unwildcarding of set fields is only done for practical reasons in the
>> userspace code, and could be optimized away, especially for recent enough
>> datapaths
User space implementation of the sample action is not consistent with
kernel datapath. In kernel datapath, the side effects of actions
within the sample actions are not visible to the subsequent actions.
Current user space handling does not follow the same logic. This patch
makes them consistent.
Signed-off-by: Shashank Ram
---
datapath-windows/ovsext/Vport.c | 6 ++
datapath-windows/ovsext/Vport.h | 2 ++
2 files changed, 8 insertions(+)
diff --git a/datapath-windows/ovsext/Vport.c b/datapath-windows/ovsext/Vport.c
index e9e22aa..9142937 100644
---
On 11 January 2017 at 02:20, Paul Blakey wrote:
>
>
> On 10/01/2017 23:58, Joe Stringer wrote:
>>
>> On 10 January 2017 at 06:36, Paul Blakey wrote:
>>>
>>>
>>>
>>> On 06/01/2017 01:28, Joe Stringer wrote:
On 25 December 2016 at 03:39, Paul
On 10 January 2017 at 16:02, Jarno Rajahalme wrote:
> In the worst case this patch will introduce rate-limited logging for other
> states than UKEY_OPERATIONAL that may want to transition onto themselves, so:
>
> Acked-by: Jarno Rajahalme
Thanks. I have reasonable
Hi Joe,
On 11.01.2017 23:30, Joe Stringer wrote:
On 11 January 2017 at 02:47, Valentine Sinitsyn
wrote:
Hi all,
I'm struggling to find an answer to a seemingly simple question: why does
"ct(nat)" action need to update the flow key after NAT (see
Dear Sir / Madam,
It is my great privilege for me to invite you to 2017 Global Youths
conferences which will be held from 21st - 25th of February 2017 at the
{Atlanta Georgia Convention Center United States of America, The organizing
committee is responsible for all visa arrangements to the
On 11 January 2017 at 02:47, Valentine Sinitsyn
wrote:
> Hi all,
>
> I'm struggling to find an answer to a seemingly simple question: why does
> "ct(nat)" action need to update the flow key after NAT (see
> ovs_nat_update_key())?
>
> My confusion comes from the
Small fix on the comments about the DPDK buffer data to refer
to dp_packet_init_dpdk() function.
Signed-off-by: Antonio Fischetti
---
lib/dp-packet.c | 4 ++--
lib/dp-packet.h | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/lib/dp-packet.c
On 01/11/2017 03:05 PM, Loftus, Ciara wrote:
>>
>> Binbin Xu writes:
>>
>>> After the commit "55e075e65ef9ecbd70e5e0fada2704c3d73724d8
>>> netdev-dpdk: Arbitrary 'dpdk' port naming", we could hotplug
>>> attach DPDK ports specified via the 'dpdk-devargs' option.
>>>
>>> But
Mesos looks to have provided the plugin ability for north/south
connectivity.
http://mesos.apache.org/documentation/latest/cni/#a-port-mapper-plugin
On 6 December 2016 at 23:36, Salvatore Orlando
wrote:
> I am unfortunately not very up-to-date with Mesos, but I reckon
>
> Since 55e075e65ef9("netdev-dpdk: Arbitrary 'dpdk' port naming"),
> set_config() is used to identify a DPDK device, so it's better to report
> its detailed error message to the user. Tunnel devices and patch ports
> rely a lot on set_config() as well.
>
> This commit adds a param to
>
> Binbin Xu writes:
>
> > After the commit "55e075e65ef9ecbd70e5e0fada2704c3d73724d8
> > netdev-dpdk: Arbitrary 'dpdk' port naming", we could hotplug
> > attach DPDK ports specified via the 'dpdk-devargs' option.
> >
> > But the socket id of DPDK ports can't be assigned
Hi everyone, we are facing a flopping of igb (5.3.4.4) nics which are
bonded by using openvswitch. I am in XenServer which is based on CentOS. I
am not sure if the problem is the driver or openvswitch. We have six nics
that are bonded into two groups of three. The issue appers after some time
that
The default slave node connect to the master node using TCP, and the pacemaker
can not modify the protocol and port of the connection.
Add pacemaker parameters to support the connection of the slave node to the
master node using a different protocol and port.
Signed-off-by: Guoshuai Li
On 01/07/2017 01:24 AM, Daniele Di Proietto wrote:
> Since 55e075e65ef9("netdev-dpdk: Arbitrary 'dpdk' port naming"),
> set_config() is used to identify a DPDK device, so it's better to report
> its detailed error message to the user. Tunnel devices and patch ports
> rely a lot on set_config() as
Hi,
Please be invited to the first sync meeting in the new year.
Agenda:
* Status/progress/coordination of work packages:
1 - L3 packets in kernel datapath (net-next)
2 - Layer 3 tunnel configuration
3 - L3 ports in non-PTAP bridge
6 - VXLAN-GPE tunnel
4 -
Hi all,
I'm struggling to find an answer to a seemingly simple question: why
does "ct(nat)" action need to update the flow key after NAT (see
ovs_nat_update_key())?
My confusion comes from the following scenario. Consider the first
to-be-NATed packet coming. There is no datapath flow
On 11/01/2017 00:34, Joe Stringer wrote:
On 10 January 2017 at 07:50, Paul Blakey wrote:
+nl_msg_put_u32(, OVS_ACTION_ATTR_OUTPUT, ifindex_out);
+if (tnl_cfg && tnl_cfg->dst_port != 0) {
+nl_msg_put_u32(, OVS_TUNNEL_KEY_ATTR_TP_DST,
Sehr geehrte Damen und Herren,
Ich benötige Ihre Unterstützung in Ihrem Land, um zu verlagern und zu
investieren. Ich bitte Sie um Hilfe, weil ich nicht weiß
Business und die Regeln, die Ihr Land zu einer sicheren Investition führen wird.
Willst du versprechen, aufrichtig mit mir zu sein?
25 matches
Mail list logo