On Sun, Mar 17, 2019 at 05:58:47AM +, Roi Dayan wrote:
>
>
> On 14/03/2019 10:50, Simon Horman wrote:
> > On Tue, Mar 12, 2019 at 04:05:16PM +0100, Simon Horman wrote:
> >> On Mon, Mar 11, 2019 at 03:25:09PM +, John Hurley wrote:
> >>> On Mon, Mar 11, 2019 at 2:34 PM Roi Dayan wrote:
> >
On 14/03/2019 10:50, Simon Horman wrote:
> On Tue, Mar 12, 2019 at 04:05:16PM +0100, Simon Horman wrote:
>> On Mon, Mar 11, 2019 at 03:25:09PM +, John Hurley wrote:
>>> On Mon, Mar 11, 2019 at 2:34 PM Roi Dayan wrote:
It could be a port added to ovs bridge already has ingress qdis
On Tue, Mar 12, 2019 at 04:05:16PM +0100, Simon Horman wrote:
> On Mon, Mar 11, 2019 at 03:25:09PM +, John Hurley wrote:
> > On Mon, Mar 11, 2019 at 2:34 PM Roi Dayan wrote:
> > >
> > > It could be a port added to ovs bridge already has ingress qdisc
> > > which will make the block probe fail.
On 12/03/2019 17:05, Simon Horman wrote:
> On Mon, Mar 11, 2019 at 03:25:09PM +, John Hurley wrote:
>> On Mon, Mar 11, 2019 at 2:34 PM Roi Dayan wrote:
>>>
>>> It could be a port added to ovs bridge already has ingress qdisc
>>> which will make the block probe fail.
>>> The probes should st
On Mon, Mar 11, 2019 at 03:25:09PM +, John Hurley wrote:
> On Mon, Mar 11, 2019 at 2:34 PM Roi Dayan wrote:
> >
> > It could be a port added to ovs bridge already has ingress qdisc
> > which will make the block probe fail.
> > The probes should start clean and ingress is being added later
> >
On Mon, Mar 11, 2019 at 2:34 PM Roi Dayan wrote:
>
> It could be a port added to ovs bridge already has ingress qdisc
> which will make the block probe fail.
> The probes should start clean and ingress is being added later
> so just remove ingress in case it exists.
>
> Signed-off-by: Roi Dayan
It could be a port added to ovs bridge already has ingress qdisc
which will make the block probe fail.
The probes should start clean and ingress is being added later
so just remove ingress in case it exists.
Signed-off-by: Roi Dayan
---
lib/netdev-tc-offloads.c | 3 +++
1 file changed, 3 inserti
