From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH 1/2] virtio: initialize iopl when device is initialized Date: Fri, 6 Mar 2015 08:55:14 -0800 Message-ID: <20150306085514.1b0ecbd2@urahara> References: <1425602726-26538-1-git-send-email-stephen@networkplumber.org> <1425602726-26538-2-git-send-email-stephen@networkplumber.org> <20150306082057.5c505f54@urahara> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev-VfR2kkLFssw@public.gmane.org" To: David Marchand Return-path: In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Fri, 6 Mar 2015 17:33:58 +0100 David Marchand wrote: > Is eth_virtio_dev_init() not a better place rather than eal ? > > I prefer avoiding #ifdef pmd in eal. No virtio_dev_init is called too late, after interrupt handling threads are spawned. /* Launch threads, called at application init(). */ int rte_eal_init(int argc, char **argv) { int i, fctret, ret; ... if (rte_eal_intr_init() < 0) rte_panic("Cannot init interrupt-handling thread\n"); ... if (rte_eal_dev_init() < 0) rte_panic("Cannot init pmd devices\n"