DPDK patches and discussions
 help / color / mirror / Atom feed
From: r k <rkerur@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Q on consolidating linuxapp/bsdapp in eal
Date: Fri, 21 Nov 2014 10:13:59 -0800	[thread overview]
Message-ID: <CAFb4SLC+8Sf5=E-8AtQ8ki976peXKr=WtjgjU7X6cAT4iC3HJA@mail.gmail.com> (raw)

Hi,

Thanks to Thomas for providing some inputs on this.

I am looking at consolidating common code in linuxapp/bsdapp in
librte_eal. I have started with header files and had some questions
related to it.

1. For some header files for e.g. eal_internal_cfg.h, there are very
minor differences between linux and bsd. In these cases is it ok to
separate out code in header files using
RTE_EXEC_ENV_BSDAPP/RTE_EXEC_ENV_LINUXAPP after moving to common
directory?

2. Files with same names for e.g. rte_lcore.h/rte_per_lcore.h are
present in multiple directories
            in librte_eal/common/include
            in librte_eal/[linuxapp/bsdapp]/eal/include/exec-env
     Not sure which one is the latest and should be referenced.

Inputs appreciated.

Thanks,
Ravi

             reply	other threads:[~2014-11-21 18:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 18:13 r k [this message]
2014-11-21 18:23 ` Thomas Monjalon
2014-11-21 18:48   ` r k

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='CAFb4SLC+8Sf5=E-8AtQ8ki976peXKr=WtjgjU7X6cAT4iC3HJA@mail.gmail.com' \
    --to=rkerur@gmail.com \
    --cc=dev@dpdk.org \
    /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).