From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Jay Rolette <rolette@infiniteio.com>,
"Wodkowski, PawelX" <pawelx.wodkowski@intel.com>
Cc: Dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] replaced O(n^2) sort in sort_by_physaddr() with qsort() from standard library
Date: Mon, 15 Dec 2014 14:55:36 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B03447CC64@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CADNuJVr3oaAYRuWD29N1j=ZW4TMX_X83K_mxanfR7gOq7mhW9w@mail.gmail.com>
Interestingly, in 64-bit mode the default size of operands on IA is still 32-bit. Instructions often need to have the REX prefix on them to actually use 64-bit data. The REX prefix is explained in section 2.2.1 of the "Intel® 64 and IA-32 Architectures Software Developer’s Manual", Volume 2
Regards,
/Bruce
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jay Rolette
Sent: Monday, December 15, 2014 2:29 PM
To: Wodkowski, PawelX
Cc: Dev
Subject: Re: [dpdk-dev] [PATCH] replaced O(n^2) sort in sort_by_physaddr() with qsort() from standard library
FWIW, it surprised the heck out of me as well.
Turns out that even though I'm compiling in 64-bit mode, gcc has
sizeof(int) as 4 bytes rather than 8. Not really sure what the scoop is on that, but the standard leaves that up to the compiler. I'm used to int always being the "natural size" on the CPU/OS, so for a 64-bit executable on Intel, I assumed int would be 64-bit.
Being an embedded developer for so many years, I rarely use semi-defined data types just to avoid these sorts of problems.
On Mon, Dec 15, 2014 at 7:20 AM, Wodkowski, PawelX < pawelx.wodkowski@intel.com> wrote:
>
> > Because it doesn't work correctly :-)
>
> It should, what I am missing here? :P
>
> Pawel
>
>
next prev parent reply other threads:[~2014-12-15 14:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 16:05 Jay Rolette
2014-12-15 9:05 ` Wodkowski, PawelX
2014-12-15 13:17 ` Jay Rolette
2014-12-15 13:20 ` Wodkowski, PawelX
2014-12-15 14:29 ` Jay Rolette
2014-12-15 14:55 ` Richardson, Bruce [this message]
2014-12-15 14:24 ` Ananyev, Konstantin
2014-12-16 18:39 ` Ananyev, Konstantin
2014-12-16 19:18 ` Jay Rolette
2014-12-16 19:20 ` Jay Rolette
2014-12-17 11:00 ` Ananyev, Konstantin
2014-12-17 13:08 ` Qiu, Michael
2014-12-17 13:35 ` Jay Rolette
2014-12-17 13:31 Jay Rolette
2014-12-17 14:27 ` Thomas Monjalon
2014-12-17 15:07 ` Jay Rolette
2014-12-17 15:27 ` Bruce Richardson
2015-09-09 10:35 ` Gonzalez Monroy, Sergio
2015-09-10 11:49 ` Jay Rolette
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=59AF69C657FD0841A61C55336867B5B03447CC64@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=pawelx.wodkowski@intel.com \
--cc=rolette@infiniteio.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).