[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180104065702.GH2067@nanopsycho.orion>
Date: Thu, 4 Jan 2018 07:57:02 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Jakub Kicinski <kubakici@...pl>
Cc: David Ahern <dsahern@...il.com>, netdev@...r.kernel.org,
davem@...emloft.net, jhs@...atatu.com, xiyou.wangcong@...il.com,
mlxsw@...lanox.com, andrew@...n.ch,
vivien.didelot@...oirfairelinux.com, f.fainelli@...il.com,
michael.chan@...adcom.com, ganeshgr@...lsio.com,
saeedm@...lanox.com, matanb@...lanox.com, leonro@...lanox.com,
idosch@...lanox.com, simon.horman@...ronome.com,
pieter.jansenvanvuuren@...ronome.com, john.hurley@...ronome.com,
alexander.h.duyck@...el.com, ogerlitz@...lanox.com,
john.fastabend@...il.com, daniel@...earbox.net
Subject: Re: [patch net-next v4 00/10] net: sched: allow qdiscs to share
filter block instances
Thu, Jan 04, 2018 at 12:51:52AM CET, kubakici@...pl wrote:
>On Wed, 3 Jan 2018 18:22:09 +0100, Jiri Pirko wrote:
>> However I don't agree about breaking the existing filter add and show
>> and also imposibility to make not-shared block shared in the runtime
>> before defining it first.
>
>FWIW I would agree with David that allowing add on a shared block
>modify filters on another interface can break existing users. (No
>opinion on dump and lifetime).
I don't think that David is saying that, but why do you think it would
break existing users?
Powered by blists - more mailing lists