[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200330.174944.1829532392145435132.davem@davemloft.net>
Date: Mon, 30 Mar 2020 17:49:44 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: stefano.salsano@...roma2.it
Cc: kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org,
dav.lebrun@...il.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, leon@...nel.org, ast@...nel.org,
daniel@...earbox.net, kafai@...com, songliubraving@...com,
yhs@...com, andriin@...com, bpf@...r.kernel.org,
paolo.lungaroni@...t.it, ahmed.abdelsalam@...i.it
Subject: Re: [net-next] seg6: add support for optional attributes during
behavior construction
From: Stefano Salsano <stefano.salsano@...roma2.it>
Date: Tue, 31 Mar 2020 01:23:48 +0200
> Of course a new application (e.g. iproute2, pyroute) using a new optional
> parameter will not work on older kernels, but simply because the new parameter
> is not supported. It will not work even without our proposed patch.
>
> On the other hand, we think that the solution in the patch is more backward
> compatible. Without the patch, if we define new attributes, old applications
> (e.g. iproute2 scripts) will not work on newer kernels, while with the optional
> attributes approach proposed in the patch they will work with no issues !
Translation: You want to add backwards compatibility problems because
otherwise you'll have to add backwards compatibility problems.
Sorry, I'm still not convinced.
You must find another way to achieve your objective.
Powered by blists - more mailing lists