Re: [ovs-dev] [PATCH] rhel: fix the exit status of the openvswitch init script.

2013-10-01 Thread Paul Ingram
he final exit status for the entire construct. > someprog is executed. The exit status is taken in #part5. The stdout is taken > by the pipe in#part4 and forwarded to filter. The output from filter will in > turn reach stdout as explained in#part4 > > > On 10/01/2013 03:34 PM, Pa

Re: [ovs-dev] [PATCH] rhel: fix the exit status of the openvswitch init script.

2013-10-01 Thread Paul Ingram
Why the redirect from descriptor 4? :: psi On Oct 1, 2013, at 3:13 PM, Duffie Cooley wrote: > What about this? > > referenced from here. > > http://unix.stackexchange.com/questions/14270/get-exit-status-of-process-thats-piped-to-another/70675#70675 > > diff --git a/utilities/ovs-lib.in b/uti

Re: [ovs-dev] [PATCH] vlog: Fix formatting of milliseconds in Python log messages.

2013-09-17 Thread Paul Ingram
Thanks guys. :: psi On Sep 17, 2013, at 10:05 AM, Ben Pfaff wrote: > On Tue, Sep 17, 2013 at 09:59:58AM -0700, Gurucharan Shetty wrote: >> On Mon, Sep 16, 2013 at 3:15 PM, Ben Pfaff wrote: >>> Commit 2b31d8e713de7 (vlog: Report timestamps in millisecond resolution in >>> log messages.) introdu

[ovs-dev] [PATCH v2 2/2] ovsdb: write commit timestamps to millisecond resolution.

2013-09-13 Thread Paul Ingram
lem. 2. When an old ovsdb-tool reads a new database, it will interpret the millisecond timestamps as seconds and report dates in the far future; the time of this commit is reported as the year 45672 (each second since the epoch is interpreted as 16 minutes). Signed-off-by: Paul Ingram ---

[ovs-dev] [PATCH v2 1/2] ovsdb: use monotonic time to calculate database compaction interval

2013-09-13 Thread Paul Ingram
calculates the next compaction time based on the time when the database was first loaded or the last compaction was done, both in monotonic time at millisecond resolution. Signed-off-by: Paul Ingram --- ovsdb/file.c | 46 -- 1 file changed, 16

[ovs-dev] [PATCH v2 0/2] millisecond timestamps in ovsdb transactions

2013-09-13 Thread Paul Ingram
The commits in this series are a reworked form of the second commit 'ovsdb: timestamp database records to millisecond resolution' from v1 of this series. Paul Ingram (2): ovsdb: use monotonic time to calculate database compaction interval ovsdb: write commit timestamps to m

Re: [ovs-dev] [PATCH 1/2] Report timestamps in millisecond resolution in log messages.

2013-09-12 Thread Paul Ingram
I just noticed that you fixed a silly error in ovsdb/ovsdb-tool.c that I introduced in my original patch. Thanks for that :: psi On Sep 12, 2013, at 6:23 PM, Paul Ingram wrote: > On Sep 11, 2013, at 10:39 PM, Ben Pfaff wrote: > >> It's reasonable enough. >> >

Re: [ovs-dev] [PATCH 2/2] ovsdb: timestamp database records to millisecond resolution.

2013-09-12 Thread Paul Ingram
On Sep 11, 2013, at 10:41 PM, Ben Pfaff wrote: > > This patch also needs your sign-off. OK, included with sign-off and a check which I mysteriously left out of the original patch. Thanks. :: psi --8<--cut here-->8-- From: Paul

Re: [ovs-dev] [PATCH 1/2] Report timestamps in millisecond resolution in log messages.

2013-09-12 Thread Paul Ingram
s[4]; -char *d, *p; +char *p; sprintf(decimals, "%03d", tm->msec); -d = decimals; for (p = strchr(s, '#'); p; p = strchr(p, '#')) { -*p++ = *d ? *d++ : '0'; +char *d = decimals; +whil

[ovs-dev] [PATCH 2/2] ovsdb: timestamp database records to millisecond resolution.

2013-09-09 Thread Paul Ingram
The ovsdb-server compaction timing logic is written assuming milliscond resolution timestamps but ovsdb-server wrote second resolution timestamps. This commit changes ovsdb-server to write millisecond resolution timestamps and ovsdb-tool to report millisecond timestamps. This raises two compatibi

[ovs-dev] [PATCH 1/2] Report timestamps in millisecond resolution in log messages.

2013-09-09 Thread Paul Ingram
To make debugging easier. --- lib/dynamic-string.c | 21 +++-- lib/dynamic-string.h |7 ++--- lib/table.c |2 +- lib/timeval.c | 79 + lib/timeval.h |9 ++ lib/vlog.c| 16 +

[ovs-dev] [PATCH 2/2] ovsdb: timestamp database records to millisecond resolution.

2013-09-08 Thread Paul Ingram
The ovsdb-server compaction timing logic is written assuming milliscond resolution timestamps but ovsdb-server wrote second resolution timestamps. This commit changes ovsdb-server to write millisecond resolution timestamps and ovsdb-tool to report millisecond timestamps. This raises two compatibi

[ovs-dev] [PATCH 1/2] Report timestamps in millisecond resolution in log messages.

2013-09-08 Thread Paul Ingram
To make debugging easier. --- lib/dynamic-string.c | 21 +++-- lib/dynamic-string.h |7 ++--- lib/table.c |2 +- lib/timeval.c | 79 + lib/timeval.h |9 ++ lib/vlog.c| 16 +

Re: [ovs-dev] [PATCH] Adds way to determine db changes from Idl.run()

2013-08-07 Thread Paul Ingram
NVPd also calls idl.run() :: psi On Aug 7, 2013, at 1:37 PM, Reid Price wrote: > I like this one better. I am surprised that test-ovsdb has the only > invocations of idl.run(), but if that is true, LGTM. > > > On Tue, Aug 6, 2013 at 3:14 PM, Aaron Rosen wrote: > This patch changes what is

[ovs-dev] [PATCH] cfm: update remote opstate only when a CCM is received.

2013-08-02 Thread Paul Ingram
last remote opstate for a CFM interface and only change it when a CCM arrives signaling a change. Bug #18806 Signed-off-by: Paul Ingram --- lib/cfm.c | 16 +--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/lib/cfm.c b/lib/cfm.c index 235d121..a7cc890 100644 --- a

Re: [ovs-dev] [PATCH 3/3] ofp-parse: Add support for dl_dst masks in flow match parsing.

2011-06-08 Thread Paul Ingram
faff wrote: >>> This makes it possible to add flows that match on the Ethernet multicast >>> bit with ovs-ofctl. >>> >>> CC: Paul Ingram >>> CC: Amar Padmanabhan ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev