From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <a.pollenus@deltacast.tv>
Received: from mail.deltatec.be (mxbackup1.deltatec.be [62.197.119.12])
 by dpdk.org (Postfix) with ESMTP id 03B6E2AA0
 for <users@dpdk.org>; Fri,  7 Sep 2018 12:38:49 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=deltacast.tv;
 s=AnsUTM; 
 h=MIME-Version:Content-Type:Message-ID:Date:Subject:To:From;
 bh=GdyTto2HnFMYySISFEOJ/8pn5oqJoh1dJS/rsYv7Ktw=; 
 b=PcWg0Ty2IrM2BGTxdsb3tI8AcskL4ajDKNko/wi7HyKAVn1a279EfsrRB+OLFq85zHPBCzgJ71NucF6vkZ0BNwCrTQqNFV5lcw2EutTZ5EdVc0oYQgrIr180HCEElx6DKhl5go9YNTYQD3WWx6HdcuqDoN56r09bPZAd9anNLy4=;
Received: from [172.16.4.5] (port=40551 helo=W2K16-SVR-5.office.deltatec.net)
 by mail.deltatec.be with esmtps (TLSv1.2:AES256-GCM-SHA384:256)
 (Exim 4.82_1-5b7a7c0-XX) (envelope-from <a.pollenus@deltacast.tv>)
 id 1fyE9o-0004CT-10
 for users@dpdk.org; Fri, 07 Sep 2018 12:38:32 +0200
Received: from W2K16-SVR-5.office.deltatec.net (172.16.4.5) by
 W2K16-SVR-5.office.deltatec.net (172.16.4.5) with Microsoft SMTP Server
 (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id
 15.1.1034.26; Fri, 7 Sep 2018 12:38:32 +0200
Received: from W2K16-SVR-5.office.deltatec.net ([::1]) by
 W2K16-SVR-5.office.deltatec.net ([::1]) with mapi id 15.01.1034.026; Fri, 7
 Sep 2018 12:38:32 +0200
X-CTCH-RefID: str=0001.0A0B0205.5B925531.0064, ss=1, re=0.000, recu=0.000,
 reip=0.000, cl=1, cld=1, fgs=0
From: Antoine POLLENUS <a.pollenus@deltacast.tv>
To: "users@dpdk.org" <users@dpdk.org>
Thread-Topic: [dpdk-users] Running a second DPDK process that prints the NIC's
 link status/speed causes the first DPDK process to stop
 transmitting.
Thread-Index: AdRGldUrV85hZHZYThukNZxCRAyl2g==
Date: Fri, 7 Sep 2018 10:38:32 +0000
Message-ID: <5b2991fd3fd341bfa8b09a414f5f54f6@deltacast.tv>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.16.6.165]
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [dpdk-users] Running a second DPDK process that prints the
 NIC's link status/speed causes the first DPDK process to stop transmitting.
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2018 10:38:50 -0000

Francis

You should read these 2 resources  on how DPDK multi process works:

https://doc.dpdk.org/guides/prog_guide/multi_proc_support.html

https://doc.dpdk.org/guides/sample_app_ug/multi_process.html

and most specifically this one :

https://doc.dpdk.org/guides/prog_guide/multi_proc_support.html#multi-proces=
s-limitations

The delivery of interrupts, such as Ethernet* device link status interrupts=
, do not work in secondary processes. All interrupts are triggered inside t=
he primary process only. Any application needing interrupt notification in =
multiple processes should provide its own mechanism to transfer the interru=
pt information from the primary process to any secondary process that needs=
 the information.


Regards

Antoine