DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Alex Ciobotaru <alex.ciobotaru@gmail.com>
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:04:21 +0200	[thread overview]
Message-ID: <1899920.NzqdMBxxeb@xps> (raw)
In-Reply-To: <9d7c6bbf-4c14-d68e-3b17-87ef73a71303@gmail.com>

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.

      reply	other threads:[~2018-05-22 21:04 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
2018-05-22 21:04       ` Thomas Monjalon [this message]

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=1899920.NzqdMBxxeb@xps \
    --to=thomas@monjalon.net \
    --cc=alex.ciobotaru@gmail.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.com \
    /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).