DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ravi Kerur <rkerur@gmail.com>
Cc: dev@dpdk.org, rkerur@brocade.com
Subject: Re: [dpdk-dev] [PATCH v4 0/7] Move EAL common function
Date: Mon, 30 Mar 2015 23:29:40 +0200	[thread overview]
Message-ID: <1722908.xonNXe7smH@xps13> (raw)
In-Reply-To: <1420565095-17278-1-git-send-email-rkerur@gmail.com>

Hi Ravi,

2015-01-06 12:24, Ravi Kerur:
> Fix v3 PATCH review comments from Thomas.
> eal_common.c is further split into eal_common_system.c and
> eal_common_runtime.c files with appropriate functions.
> eal_externs.h file is removed and _get_ and _set_ APIs are
> used to access variables.
> Functions with same signature in Linux and BSD but different
> names are kept intact but Linux function name is used as
> wrapper for BSD.
> Added eal_pci.c in v4 PATCH.
> New files added follow _common_ naming conventions.
> Tested against Ubuntu and FreeBSD.
> 
> Ravi Kerur (7):
>   Move common functions in eal_debug.c
>   Move common functions in eal_thread.c
>   Move common functions in eal.c
>   Move common functions in eal_lcore.c
>   Move common functions in eal_timer.c
>   Move common functions in eal_memory.c
>   Move common functions in eal_pci.c

Sorry for not integrating this big refactoring in release 2.0.
It wasn't easy to merge it during development of some EAL features.
And it's now too risky to rework it before the release.
I think this clean-up is needed and should be done at the beginning of 2.1
cycle. We just need to rebase it and remove the "ifdef BSD/LINUX" which was
introduced in pci code.

Do you think you'll have time for it?

Thanks

  reply	other threads:[~2015-03-30 21:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 17:24 Ravi Kerur
2015-03-30 21:29 ` Thomas Monjalon [this message]
2015-03-30 23:15   ` Ravi Kerur
2015-03-30 23:24     ` Thomas Monjalon
2015-03-31 18:39       ` Ravi Kerur
2015-04-09 19:45         ` Ravi Kerur
2015-01-06 17:26 Ravi Kerur

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=1722908.xonNXe7smH@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=rkerur@brocade.com \
    --cc=rkerur@gmail.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).