On 11 December 2014 at 19:34, Joe Stringer wrote:
> On 11 December 2014 at 16:41, Ben Pfaff wrote:
>> On Fri, Dec 05, 2014 at 11:45:11AM -0800, Joe Stringer wrote:
>>> Parse "ufid:" at the beginning of a flow specification and use it
>>> for flow manipulation if present.
>>>
>>> Signed-off-by: Jo
On 11 December 2014 at 16:41, Ben Pfaff wrote:
> On Fri, Dec 05, 2014 at 11:45:11AM -0800, Joe Stringer wrote:
>> Parse "ufid:" at the beginning of a flow specification and use it
>> for flow manipulation if present.
>>
>> Signed-off-by: Joe Stringer
>> ---
>> v3: Fix build on windows.
>> v2: Reb
On Fri, Dec 05, 2014 at 11:45:11AM -0800, Joe Stringer wrote:
> Parse "ufid:" at the beginning of a flow specification and use it
> for flow manipulation if present.
>
> Signed-off-by: Joe Stringer
> ---
> v3: Fix build on windows.
> v2: Rebase.
I'd be at least half-inclined to always print ufid
Parse "ufid:" at the beginning of a flow specification and use it
for flow manipulation if present.
Signed-off-by: Joe Stringer
---
v3: Fix build on windows.
v2: Rebase.
---
lib/dpctl.c| 41 +
lib/odp-util.c | 35 +++