From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: DPDK and forked processes
Date: Fri, 27 Jul 2018 08:59:50 -0700
Message-ID: <20180727085950.2e2e0281@xeon-e3>
References: <9184057F7FC11744A2107296B6B8EB1E446E9A79@FMSMSX108.amr.corp.intel.com>
 <e62e790d-45dc-29bb-be26-0c83a03301d2@intel.com>
 <9184057F7FC11744A2107296B6B8EB1E446F214F@FMSMSX108.amr.corp.intel.com>
 <7441138.EijKcuSYIv@xps>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "Eads, Gage" <gage.eads@intel.com>, "Burakov, Anatoly"
 <anatoly.burakov@intel.com>, "dev@dpdk.org" <dev@dpdk.org>, "Richardson,
 Bruce" <bruce.richardson@intel.com>, "jerin.jacob@caviumnetworks.com"
 <jerin.jacob@caviumnetworks.com>, "Yigit, Ferruh" <ferruh.yigit@intel.com>,
 "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>, "Ananyev, Konstantin"
 <konstantin.ananyev@intel.com>, Olivier Matz <olivier.matz@6wind.com>
To: Thomas Monjalon <thomas@monjalon.net>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pg1-f182.google.com (mail-pg1-f182.google.com
 [209.85.215.182]) by dpdk.org (Postfix) with ESMTP id E969D548B
 for <dev@dpdk.org>; Fri, 27 Jul 2018 17:59:53 +0200 (CEST)
Received: by mail-pg1-f182.google.com with SMTP id y5-v6so3487140pgv.1
 for <dev@dpdk.org>; Fri, 27 Jul 2018 08:59:53 -0700 (PDT)
In-Reply-To: <7441138.EijKcuSYIv@xps>
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 Fri, 27 Jul 2018 17:03:48 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:

> 27/07/2018 15:46, Eads, Gage:
> > As this discussion has broad implications for DPDK, is it a good candidate for a techboard meeting topic?   
> 
> We can discuss it in techboard, but usually we prefer discussing topics
> whose resolution is not clear.
> In this case, I think everybody agree with Anatoly, isn't it?

I would prefer that decisions like this be done by rough consensus on the mailing list.

As far as applications messing with internals, in reality any application can change
anything. Just don't come crying to DPDK community for help.