On Fri, Nov 2, 2012 at 12:44 AM, Ben Pfaff b...@nicira.com wrote:
Stepping back: I support your basic proposal, that ovs-vsctl
add-port should report a problem if the port cannot successfully be
added. The issue is that, so far, the approaches I've seen don't fit
well with the overall Open
On Nov 1, 2012, at 7:00 PM, Ben Pfaff b...@nicira.com wrote:
(There isn't any difference.)
Based on a conversation in #openvswitch.
Signed-off-by: Ben Pfaff b...@nicira.com
Acked-by: Kyle Mestery kmest...@cisco.com
___
dev mailing list
On Fri, Nov 02, 2012 at 03:28:03PM +0800, Cong Wang wrote:
On Fri, Nov 2, 2012 at 12:44 AM, Ben Pfaff b...@nicira.com wrote:
Stepping back: I support your basic proposal, that ovs-vsctl
add-port should report a problem if the port cannot successfully be
added. The issue is that, so far,
From: Shan Wei davids...@tencent.com
no change vs v1.
Lots of drivers use this kind to read/write per-cpu variable.
stats = this_cpu_ptr(dp-stats_percpu);
u64_stats_update_begin(stats-sync);
stats-tx_packets++;
u64_stats_update_begin(stats-sync);
Signed-off-by: Shan Wei
On Fri, Nov 02, 2012 at 01:18:38PM +, Kyle Mestery (kmestery) wrote:
On Nov 1, 2012, at 7:00 PM, Ben Pfaff b...@nicira.com wrote:
(There isn't any difference.)
Based on a conversation in #openvswitch.
Signed-off-by: Ben Pfaff b...@nicira.com
Acked-by: Kyle Mestery
On Thu, Nov 01, 2012 at 04:53:45PM +, Kyle Mestery (kmestery) wrote:
On Nov 1, 2012, at 2:23 AM, Ben Pfaff b...@nicira.com wrote:
ofproto has a concept of hidden OpenFlow tables. Currently these are
used internally only for ofproto-dpif for a couple of unimportant
purposes. However,
On Sat, 3 Nov 2012, Shan Wei wrote:
+++ b/net/openvswitch/datapath.c
@@ -208,7 +208,7 @@ void ovs_dp_process_received_packet(struct vport *p,
struct sk_buff *skb)
int error;
int key_len;
- stats = per_cpu_ptr(dp-stats_percpu, smp_processor_id());
+ stats =
On Mon, Oct 29, 2012 at 03:03:13PM -0500, Adam Heath wrote:
On 10/29/2012 11:34 AM, Ben Pfaff wrote:
Until now, a command like ovs-vsctl --may-exist add-br br0 yielded a
confusing error message. Users had to realize that the correct form was
ovs-vsctl -- --may-exist add-br br0, but instead
On 11/02/2012 12:49 PM, Ben Pfaff wrote:
On Mon, Oct 29, 2012 at 03:03:13PM -0500, Adam Heath wrote:
On 10/29/2012 11:34 AM, Ben Pfaff wrote:
Until now, a command like ovs-vsctl --may-exist add-br br0 yielded a
confusing error message. Users had to realize that the correct form was
ovs-vsctl
On Fri, Nov 02, 2012 at 03:40:20PM -0500, Adam Heath wrote:
On 11/02/2012 12:49 PM, Ben Pfaff wrote:
On Mon, Oct 29, 2012 at 03:03:13PM -0500, Adam Heath wrote:
On 10/29/2012 11:34 AM, Ben Pfaff wrote:
Until now, a command like ovs-vsctl --may-exist add-br br0 yielded a
confusing error
On 11/02/2012 04:19 PM, Ben Pfaff wrote:
I still don't understand. Why would an existing script call ovs-vsctl
with --may-exist as a global option? The call would not do anything
useful, because it would exit with a fatal error every time. Taking
this argument to its logical conclusion, one
On Fri, Nov 02, 2012 at 04:21:56PM -0500, Adam Heath wrote:
On 11/02/2012 04:19 PM, Ben Pfaff wrote:
I still don't understand. Why would an existing script call ovs-vsctl
with --may-exist as a global option? The call would not do anything
useful, because it would exit with a fatal error
Hello,
I'd like to invite you to our upcoming free webcast on the Top 10
Free Tools for SEO / Google Rank being held online in the next few weeks.
Register for this no cost web event on Google / SEO -
http://www.seminar-on-seo.net/1/nov3.html?dev@openvswitch.org
Google is by far the #1 way
Hello,
I am Ms. Teresa Au, HSBC Hong Kong, head of corporate sustainability
Asia pacific region. A sum of US$23,200,000.00 Million was deposited
by our Late customer who died without declaring any next of kin before
his death in 2007.
My suggestion to you is to stand as the next of kin
14 matches
Mail list logo
