From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Marchand <david.marchand@6wind.com>
Subject: Re: [PATCH v2 5/7] eal: bring forward init of interrupt
	handling
Date: Fri, 13 Jul 2018 10:09:42 +0200
Message-ID: <CALwxeUvx2UXSQLTQrSiBZvOEEqmgz9NBUxnEPxJndLcdb_2w3Q@mail.gmail.com>
References: <cover.1530009564.git.anatoly.burakov@intel.com>
 <5f6bc60bf193daf4eb07f4484c52878bb1b751de.1530009564.git.anatoly.burakov@intel.com>
 <5431396.k1M6VaMcRs@xps>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Cc: Anatoly Burakov <anatoly.burakov@intel.com>, dev@dpdk.org,
 Jianfeng Tan <jianfeng.tan@intel.com>,
 Bruce Richardson <bruce.richardson@intel.com>,
 "Ananyev, Konstantin" <konstantin.ananyev@intel.com>, qi.z.zhang@intel.com,
 Stephen Hemminger <stephen@networkplumber.org>,
 Olivier Matz <olivier.matz@6wind.com>,
 Ferruh Yigit <ferruh.yigit@intel.com>,
 Maxime Coquelin <maxime.coquelin@redhat.com>, tiwei.bie@intel.com
To: Thomas Monjalon <thomas@monjalon.net>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-yw0-f195.google.com (mail-yw0-f195.google.com
 [209.85.161.195]) by dpdk.org (Postfix) with ESMTP id 028AD1B4F4
 for <dev@dpdk.org>; Fri, 13 Jul 2018 10:10:03 +0200 (CEST)
Received: by mail-yw0-f195.google.com with SMTP id t198-v6so11451892ywc.3
 for <dev@dpdk.org>; Fri, 13 Jul 2018 01:10:03 -0700 (PDT)
In-Reply-To: <5431396.k1M6VaMcRs@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, Jul 13, 2018 at 12:36 AM, Thomas Monjalon <thomas@monjalon.net> wrote:
> I am almost sure it will bring regressions.
>
> Please think again about the consequences of initializing interrupt thread
> before affinity setting, memory init, device init.

Well, there was an issue vith virtio at one time (interrupt handler
did not have the right iopl for virtio callback).
http://git.dpdk.org/dpdk/commit/lib/librte_eal/linuxapp/eal/eal.c?id=fd6949c55c9a48e81c625138679159829d51ac51

Now... time has passed since then.
It is worth checking the issue is still here, and if it is the case,
revisit this.
I suppose virtio pmd should deal with this itself.


-- 
David Marchand