DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Qiu, Michael" <michael.qiu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Chao Zhu <chaozhu@linux.vnet.ibm.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] eal: detect endianness
Date: Thu, 4 Dec 2014 12:50:04 +0000	[thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E60286C9CC54@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1538241.xRI4LPKbTP@xps13>

On 12/4/2014 8:20 PM, Thomas Monjalon wrote:
> 2014-12-04 10:28, Qiu, Michael:
>> On 12/4/2014 5:01 PM, Thomas Monjalon wrote:
>>> 2014-12-04 02:28, Qiu, Michael:
>>>> On 12/4/2014 5:26 AM, Thomas Monjalon wrote:
>>>>> There is no standard to check endianness.
>>>>> So we need to try different checks.
>>>>> Previous trials were done in testpmd (see commits
>>>>> 51f694dd40f56 and 64741f237cf29) without full success.
>>>>> This one is not guaranteed to work everywhere so it could
>>>>> evolve when exceptions are found.
>>> [...]
>>>>>  #include <stdint.h>
>>>>> +#ifdef RTE_EXEC_ENV_BSDAPP
>>>>> +#include <sys/endian.h>
>>>>> +#else
>>>>> +#include <endian.h>
>>>>> +#endif
>>>>> +
>>>>> +/*
>>>>> + * Compile-time endianness detection
>>>>> + */
>>>>> +#define RTE_BIG_ENDIAN    1
>>>>> +#define RTE_LITTLE_ENDIAN 2
>>>>> +#if defined __BYTE_ORDER
>>>>> +#if __BYTE_ORDER == __BIG_ENDIAN
>>>>> +#define RTE_BYTE_ORDER RTE_BIG_ENDIAN
>>>>> +#elif __BYTE_ORDER == __LITTLE_ENDIAN
>>>>> +#define RTE_BYTE_ORDER RTE_LITTLE_ENDIAN
>>>>> +#endif /* __BYTE_ORDER */
>>>>> +#elif defined __BYTE_ORDER__
>>>>> +#if __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__
>>>>> +#define RTE_BYTE_ORDER RTE_BIG_ENDIAN
>>>>> +#elif __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
>>>>> +#define RTE_BYTE_ORDER RTE_LITTLE_ENDIAN
>>>>> +#endif /* __BYTE_ORDER__ */
>>>>> +#elif defined __BIG_ENDIAN__
>>>>> +#define RTE_BYTE_ORDER RTE_BIG_ENDIAN
>>>>> +#elif defined __LITTLE_ENDIAN__
>>>>> +#define RTE_BYTE_ORDER RTE_LITTLE_ENDIAN
>>>>> +#endif
>>>> What do you think about :
>>>>
>>>> +/*
>>>> +  * Compile-time endianness detection
>>>> + */
>>>> +#define RTE_BIG_ENDIAN 1
>>>> +#define RTE_LITTLE_ENDIAN 2
>>>> +if defined __BYTE_ORDER__    /* Prefer gcc build-in macros */
>>>> +#if __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__
>>>> +#define RTE_BYTE_ORDER RTE_BIG_ENDIAN
>>>> +#elif __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
>>>> +#define RTE_BYTE_ORDER RTE_LITTLE_ENDIAN
>>>> +#endif /* __BYTE_ORDER__ */
>>>> +#else
>>>> +#if defined RTE_EXEC_ENV_BSDAPP
>>>> +#include <sys/endian.h>
>>>> +#else
>>>> +#include <endian.h>
>>>> +#endif
>>>> +#if defined __BYTE_ORDER
>>>> +#if __BYTE_ORDER == __BIG_ENDIAN
>>>> +#define RTE_BYTE_ORDER RTE_BIG_ENDIAN
>>>> +#elif __BYTE_ORDER == __LITTLE_ENDIAN
>>>> +#define RTE_BYTE_ORDER RTE_LITTLE_ENDIAN
>>>> +#endif /* __BYTE_ORDER */
>>>> +#elif defined __BIG_ENDIAN__
>>>> +#define RTE_BYTE_ORDER RTE_BIG_ENDIAN
>>>> +#elif defined __LITTLE_ENDIAN__
>>>> +#define RTE_BYTE_ORDER RTE_LITTLE_ENDIAN
>>>> +#endif
>>>> +#endif
>>> Please, could you give more explanations about your proposal?
>>> Why not always try to include endian.h?
>> I assume that if gcc can handler why we need include that file?
> Separating include on top is easier to read, and I'm not sure it won't
> be needed for __BYTE_ORDER__ with some toolchains.
>
>> Also it seems that only old version could have this issue, newer
>> versions has build in this marcos.
>>
>> So that's why I prefer  "__BYTE_ORDER__" for high priority.
> I have no problem with reversing this priority.
>
>>> Why giving high priority to __BYTE_ORDER__?
> Any other comment? May I apply with above change?

Acked-by: Michael Qiu <michael.qiu@intel.com>




  reply	other threads:[~2014-12-04 12:50 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1417606044-3432-1-git-send-email-michael.qiu@intel.com>
     [not found] ` <1417606099-3489-1-git-send-email-michael.qiu@intel.com>
2014-12-03 11:42   ` [dpdk-dev] [PATCH] test-pmd: Fix pointer aliasing error Bruce Richardson
2014-12-03 13:59     ` Qiu, Michael
2014-12-03 14:51       ` Bruce Richardson
2014-12-03 15:19         ` Qiu, Michael
2014-12-03 15:36           ` Bruce Richardson
2014-12-04  2:38             ` Qiu, Michael
2014-12-04  3:28               ` [dpdk-dev] [PATCH v2] " Michael Qiu
2014-12-04  4:16                 ` [dpdk-dev] [PATCH v3] " Michael Qiu
2014-12-05  5:34                   ` Qiu, Michael
2014-12-05  9:24                     ` Thomas Monjalon
2014-12-08  1:28                       ` Qiu, Michael
2014-12-08  1:30                   ` Qiu, Michael
2014-12-10  3:44                     ` Qiu, Michael
2014-12-11  0:54                     ` Thomas Monjalon
2014-12-11 17:51                       ` r k
2014-12-12  6:49                         ` Qiu, Michael
2014-12-04 12:54                 ` [dpdk-dev] [PATCH v2] " Ananyev, Konstantin
2014-12-03 15:24     ` [dpdk-dev] [PATCH] " Olivier MATZ
2014-12-03 16:03       ` Dayu Qiu
2014-12-03 15:57     ` Dayu Qiu
2014-12-03 16:26 ` [dpdk-dev] [PATCH] test-pmd: Fix "__BYTE_ORDER__" not defined error Qiu, Michael
2014-12-03 19:59   ` Thomas Monjalon
2014-12-03 20:47     ` [dpdk-dev] [PATCH 0/2] fix endianness in EAL Thomas Monjalon
2014-12-03 20:47       ` [dpdk-dev] [PATCH 1/2] eal: detect endianness Thomas Monjalon
2014-12-04  2:28         ` Qiu, Michael
2014-12-04  9:00           ` Thomas Monjalon
2014-12-04 10:28             ` Qiu, Michael
2014-12-04 12:19               ` Thomas Monjalon
2014-12-04 12:50                 ` Qiu, Michael [this message]
2014-12-03 20:47       ` [dpdk-dev] [PATCH 2/2] app/testpmd: fix endianness detection Thomas Monjalon
2014-12-04  9:28       ` [dpdk-dev] [PATCH 0/2] fix endianness in EAL Chao Zhu
2014-12-05 16:01         ` 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=533710CFB86FA344BFBF2D6802E60286C9CC54@SHSMSX101.ccr.corp.intel.com \
    --to=michael.qiu@intel.com \
    --cc=chaozhu@linux.vnet.ibm.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).