From: Alex Ciobotaru <alex.ciobotaru@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, "Wiles, Keith" <keith.wiles@intel.com>
Subject: Re: [dpdk-dev] Question about adding a new EAL
Date: Tue, 22 May 2018 23:56:24 +0300 [thread overview]
Message-ID: <9d7c6bbf-4c14-d68e-3b17-87ef73a71303@gmail.com> (raw)
In-Reply-To: <1943193.bOZbQYoKI2@xps>
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/
>
>
next prev parent reply other threads:[~2018-05-22 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 19:23 Alexandru Ciobotaru
2018-05-22 19:53 ` Wiles, Keith
2018-05-22 19:59 ` Wiles, Keith
2018-05-22 20:18 ` Thomas Monjalon
2018-05-22 20:56 ` Alex Ciobotaru [this message]
2018-05-22 21:04 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9d7c6bbf-4c14-d68e-3b17-87ef73a71303@gmail.com \
--to=alex.ciobotaru@gmail.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).