On Wed, Sep 30, 2015 at 6:20 PM, Joe Stringer wrote:
> On 30 September 2015 at 17:31, Pravin Shelar wrote:
>> On Tue, Sep 29, 2015 at 3:39 PM, Joe Stringer wrote:
>>> Previously, if userspace specified ct_state bits in the flow key which
>>> are currently undefined (and therefore unsupported),
On 30 September 2015 at 17:31, Pravin Shelar wrote:
> On Tue, Sep 29, 2015 at 3:39 PM, Joe Stringer wrote:
>> Previously, if userspace specified ct_state bits in the flow key which
>> are currently undefined (and therefore unsupported), then they would be
>> ignored. This could cause unexpected
On Tue, Sep 29, 2015 at 3:39 PM, Joe Stringer wrote:
> Previously, if userspace specified ct_state bits in the flow key which
> are currently undefined (and therefore unsupported), then they would be
> ignored. This could cause unexpected behaviour in future if userspace is
> extended to support
On Tue, Sep 29, 2015 at 3:39 PM, Joe Stringer wrote:
> Previously, if userspace specified ct_state bits in the flow key which
> are currently undefined (and therefore unsupported), then they would be
> ignored. This could cause unexpected behaviour in future if userspace
On Wed, Sep 30, 2015 at 6:20 PM, Joe Stringer wrote:
> On 30 September 2015 at 17:31, Pravin Shelar wrote:
>> On Tue, Sep 29, 2015 at 3:39 PM, Joe Stringer wrote:
>>> Previously, if userspace specified ct_state bits in the flow
On 30 September 2015 at 17:31, Pravin Shelar wrote:
> On Tue, Sep 29, 2015 at 3:39 PM, Joe Stringer wrote:
>> Previously, if userspace specified ct_state bits in the flow key which
>> are currently undefined (and therefore unsupported), then they would
Previously, if userspace specified ct_state bits in the flow key which
are currently undefined (and therefore unsupported), then they would be
ignored. This could cause unexpected behaviour in future if userspace is
extended to support additional bits but attempts to communicate with the
current
Previously, if userspace specified ct_state bits in the flow key which
are currently undefined (and therefore unsupported), then they would be
ignored. This could cause unexpected behaviour in future if userspace is
extended to support additional bits but attempts to communicate with the
current
8 matches
Mail list logo