From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dan Gora <dg@adax.com>
Subject: Re: [PATCH v2 10/10] kni: add API to set link status on
 kernel interface
Date: Thu, 30 Aug 2018 19:11:34 -0300
Message-ID: <CAGyogRYOXDPS=nUh-eNBUDoc4MWV+B6YA3KpbabnV_aaSpvU-w@mail.gmail.com>
References: <20180628224513.18391-1-dg@adax.com>
 <20180629015508.26599-1-dg@adax.com>
 <20180629015508.26599-11-dg@adax.com> <20180829085410.4411c07e@xeon-e3>
 <CAGyogRaVWeCdEqL_-PqhMvd784axgn2ntm9ZHwBv7CNfUX0adQ@mail.gmail.com>
 <20180829150014.0ae59128@xeon-e3>
 <CAGyogRbhNrqR9xQ=0iuizbrZNtLNB4FW-CpnBDvGWCKHrSWAPg@mail.gmail.com>
 <CAGyogRbBBAU92KdqVwghpon1brMo=4XJNPotiBYpztQkzB4mGQ@mail.gmail.com>
 <20180829161043.11bb2434@xeon-e3>
 <CAF+s_Fx=x8wO5Ygxr4sxUj2G1hh+dRyFr7XiwYHL4SUPRNhX4g@mail.gmail.com>
 <CAGyogRattGkEds7dkwLmwyyfj3t0M_ygRxSJarrgLM=k3EWoiA@mail.gmail.com>
 <20180830150911.6b0e7901@xeon-e3>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Cc: Igor Ryzhov <iryzhov@nfware.com>, Ferruh Yigit <ferruh.yigit@intel.com>,
 dev@dpdk.org
To: Stephen Hemminger <stephen@networkplumber.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f68.google.com (mail-wm0-f68.google.com [74.125.82.68])
 by dpdk.org (Postfix) with ESMTP id 7B5315B2A
 for <dev@dpdk.org>; Fri, 31 Aug 2018 00:12:15 +0200 (CEST)
Received: by mail-wm0-f68.google.com with SMTP id i134-v6so2860138wmf.0
 for <dev@dpdk.org>; Thu, 30 Aug 2018 15:12:15 -0700 (PDT)
In-Reply-To: <20180830150911.6b0e7901@xeon-e3>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Thu, Aug 30, 2018 at 7:09 PM, Stephen Hemminger
<stephen@networkplumber.org> wrote:
> On Thu, 30 Aug 2018 18:41:14 -0300
> Dan Gora <dg@adax.com> wrote:
>
>> On the other hand, the "write to /sys" method is a bit more simple and
>> confines the changes to the user space library.  If we're confident
>> that the /sys ABI is stable and not going to be changed going forward
>> it seems like a valid alternative.
>
> See Documentation/ABI/testing/sysfs-class-net

yeah, but it's in the 'testing' directory :)

>>From Documentation/ABI/README:

testing/

This directory documents interfaces that are felt to be stable,
as the main development of this interface has been completed.
The interface can be changed to add new features, but the
current interface will not break by doing this, unless grave
errors or security problems are found in them.  Userspace
programs can start to rely on these interfaces, but they must be
aware of changes that can occur before these interfaces move to
be marked stable.  Programs that use these interfaces are
strongly encouraged to add their name to the description of
these interfaces, so that the kernel developers can easily
notify them if any changes occur (see the description of the
layout of the files below for details on how to do this.)

Like I said, I'm ok with using this if that's what everyone wants to do.

d