From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <alex.ciobotaru@gmail.com> Received: from mail-wm0-f67.google.com (mail-wm0-f67.google.com [74.125.82.67]) by dpdk.org (Postfix) with ESMTP id D7B6A1C0B for <dev@dpdk.org>; Tue, 22 May 2018 22:56:24 +0200 (CEST) Received: by mail-wm0-f67.google.com with SMTP id o78-v6so3470060wmg.0 for <dev@dpdk.org>; Tue, 22 May 2018 13:56:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=jpGK2nbMGuZzemnrvqIagQRQeBSZR8fuCyE4TGlQ/pE=; b=DiuyqRn8l2rrDke8neGX6hahvRUiQ6ZouAFq3YbKOC/a5k7fZ0JzgS2CkEM0mgW6ls +3m31Xo7K6hJMQoqP2CedBAsjpavXWiknCzHNndobjQ3xlzir/aHKh+EWqBLNqvTBK/s 3z6kGqBHWgCTAJQa3XR96lCC2Eb7rlIMRI6MrdB2WZ5DfEplSCrvculeQjEgLQL3TGMU 2Lg79/gEnEub20Lp+HXH8IjVW4sXTiuXwgSVmyslqZ8fp5eYn/rrFp0UoQPnMJXVH1GT sO+41rnnyVgwfQWO+nVZ4Ig93kKzpb2TvXDYcBLGkW3VkrLI5nL3bh0lcO0ZF23MMrIz Igog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=jpGK2nbMGuZzemnrvqIagQRQeBSZR8fuCyE4TGlQ/pE=; b=PMdZ83PD2c1x1xgwlv4LKTNa4yGCyXPepaSH1yU79mSXTAsvG73kpDbCqIkRm5eq1E iiqC06eJ4LYt21BbQKUoBdYxM35msfYWEe0cDGxS+1WwfRx+C+ToVPGxE+ZWyOgtPkhJ +gje8NY7tOL4JkACCqe6aizw+WQiDOElBkupqGBJDnZCQ71vKijCr1JEJ6780k89+NXZ 4TZcI2OeqIeyaamSj03gMCsaMEHsrh4J+ZR74mPMhyye/1U5QxhddIfhrOwcwmqMjg8V 05NKnV5Lfcdko/a/ubdNk6AdqO0IxctjB7goVJPyZ9q4n609v0ZrQ2YvqCWXTT6r98IH PjqA== X-Gm-Message-State: ALKqPwcHFbrpI91jG4MkP8pPHieyUyDHCEea5YlfzX1UO39+1JB5y/vb 8x7aqsMqCePj9RPt9b2+nQg= X-Google-Smtp-Source: AB8JxZrdbfyIJ3oJuydCaQaDcZ4a8SOVBu7D9nni4nGwyixM/5RpWjh+cQBTDaUveyfl9OaMuDYLpw== X-Received: by 2002:a1c:d6c9:: with SMTP id n192-v6mr2549749wmg.125.1527022584514; Tue, 22 May 2018 13:56:24 -0700 (PDT) Received: from [192.168.1.222] ([79.115.173.246]) by smtp.gmail.com with ESMTPSA id k9-v6sm16387827wre.1.2018.05.22.13.56.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 May 2018 13:56:23 -0700 (PDT) To: Thomas Monjalon <thomas@monjalon.net> Cc: dev@dpdk.org, "Wiles, Keith" <keith.wiles@intel.com> References: <CANKOshyKZACv4DSmTLcUTGxcrFNfCs3i3__HwXbjutCsZDcp+g@mail.gmail.com> <F6067F30-FB9E-42C2-82BF-606D4DF847EB@intel.com> <1943193.bOZbQYoKI2@xps> From: Alex Ciobotaru <alex.ciobotaru@gmail.com> Message-ID: <9d7c6bbf-4c14-d68e-3b17-87ef73a71303@gmail.com> Date: Tue, 22 May 2018 23:56:24 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <1943193.bOZbQYoKI2@xps> Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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 <dev.dpdk.org> List-Unsubscribe: <https://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Tue, 22 May 2018 20:56:25 -0000 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////#include <sched.h>////^////compilation terminated.////...// END OF EXCERPT/// Above I'm building (via cross toolchain) my new "xyzapp" (with its own EAL rte_*.c files) but with the inherited common headers (since the EAL/common master Makefile makes build-generated symbolic links in my build dir). So for now, I identified two quick options: - Modify the EAL headers where needed. In this case, I would remove includes such as ones above from the EAL headers, but it would probably break current supported EALs - Modify the EAL build sub-system to export my "xyzapp" (re)implemented EAL headers instead of the common ones (keeping the API, but fixing the "app" toolchain/exec-env dependencies). Basically all P headers that define the EAL would be split into M "common/generic" headers and N "app" re-implemented headers. Thank you! Alex On 22-May-18 11:18 PM, Thomas Monjalon wrote: > 22/05/2018 21:59, Wiles, Keith: >> You may want to do an RFC email subject to discuss your ideas on changing EAL code first to eliminate extra work. > Yes, definitely, RFC with first ideas can help to discuss. > > One more pointer, Windows support in progress: > http://dpdk.org/browse/draft/dpdk-draft-windows/ > >