From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 34C8C1D9E for ; Tue, 22 May 2018 23:04:24 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B1CD521B8B; Tue, 22 May 2018 17:04:23 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 22 May 2018 17:04:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=JE17PeL9cMPD32H/Y9zhIDA+WD k+na5XEiCLBa/+JAo=; b=UCQVStZOErwdZ7nSKT8/bDU9QDJfOWg0BM9YOxCtCy 28n4TK4/Yrev5Jz4uROZtRp4y9gZfDlvONBfWLnPiCQAueNqT/gL7AzsvqgpHvWt Ro2vmnigoyGWJpphddUb24aYG4KzogMoVm4ImIUbQI5jYU6C9TercrA0wy3s4C3i A= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=JE17Pe L9cMPD32H/Y9zhIDA+WDk+na5XEiCLBa/+JAo=; b=Ip3KoesJcQHiWJXEEf5UW+ fCBRXwAhZbrjZ3yxA2pvPaEiiHIb5DfyKDc9KEGxQJlOYrJN8wZX2FnoduETn0I/ hzyC5kFvar4xkCXQhq829ZzYe4miMblhZVvqxBeuG5YEsU3zdaQjpiF6S6nKBmYu aXrblou7TKqeKGBkni6VpF3xl04zk8z6xt4v5iSYpacMHaV5kg5ngWtNOKDfysgw +aLQYFuZQRqAerhneiePlDlQ7wYuigXqHyzxDImxORK6gLcCBnDznUiG5O7Mqv9k rVkg/UB7btu/BYMAdTJ4n8RHIHkGK3ewhHcgsjPmgl6qdiQZAixSVYcy5befK+Jg == X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 19357E4434; Tue, 22 May 2018 17:04:23 -0400 (EDT) From: Thomas Monjalon To: Alex Ciobotaru Cc: dev@dpdk.org, "Wiles, Keith" Date: Tue, 22 May 2018 23:04:21 +0200 Message-ID: <1899920.NzqdMBxxeb@xps> In-Reply-To: <9d7c6bbf-4c14-d68e-3b17-87ef73a71303@gmail.com> References: <1943193.bOZbQYoKI2@xps> <9d7c6bbf-4c14-d68e-3b17-87ef73a71303@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] Question about adding a new EAL X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2018 21:04:24 -0000 22/05/2018 22:56, Alex Ciobotaru: > Guys, thank you for the info so far (sorry about the HTML thing). > I will put some further insight/closure into this thread. > So, my query started from the fact that when developing a new EAL > in DPDK using an external toolchain and/or for a new OS, > the "common" (generic) part of the EAL is actually Linux/BSD bound: > > ...// START OF EXCERPT > dpdk/build/include/rte_eal.h:15:19: fatal error: > sched.h: No such file or directory So you want to port DPDK to a non-POSIX OS? If it is considered an interesting OS, we could move some POSIX parts out of the common files.