From: Ralf Hoffmann <ralf.hoffmann@allegro-packets.com>
To: sergio.gonzalez.monroy@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/1] change hugepage sorting to avoid overlapping memcpy
Date: Tue, 5 Jan 2016 10:25:12 +0100 [thread overview]
Message-ID: <1451985913-16235-1-git-send-email-ralf.hoffmann@allegro-packets.com> (raw)
In-Reply-To: <55EEEF99.2000708@intel.com>
Hi,
I want to catch up with the patch about the overlapping memory
areas/hugepage sorting. I have incorporated the qsort patch from Jay
and made the suggested changes. So this fixes both the valgrind
warning about the overlapping memcpy and possible performance problems
due to the bubblesort.
Best Regards,
Ralf
---
Ralf Hoffmann (1):
change hugepage sorting to avoid overlapping memcpy
lib/librte_eal/linuxapp/eal/eal_memory.c | 60 ++++++++------------------------
1 file changed, 14 insertions(+), 46 deletions(-)
--
2.5.0
next prev parent reply other threads:[~2016-01-05 9:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 10:14 [dpdk-dev] [PATCH v1] " Ralf Hoffmann
2015-09-08 12:45 ` Gonzalez Monroy, Sergio
2015-09-08 13:29 ` Jay Rolette
2015-09-08 14:24 ` Gonzalez Monroy, Sergio
2016-01-05 9:25 ` Ralf Hoffmann [this message]
2016-01-05 9:25 ` [dpdk-dev] [PATCH v2 1/1] " Ralf Hoffmann
2016-01-05 9:37 ` [dpdk-dev] [PATCH v3 0/1] eal/linux: " Ralf Hoffmann
2016-01-05 9:37 ` [dpdk-dev] [PATCH v3 1/1] " Ralf Hoffmann
2016-01-07 9:33 ` Sergio Gonzalez Monroy
2016-01-07 9:51 ` Sergio Gonzalez Monroy
2016-01-07 10:38 ` Sergio Gonzalez Monroy
2016-01-07 13:58 ` Ralf Hoffmann
2016-01-07 13:59 ` [dpdk-dev] [PATCH v4 1/1] " Ralf Hoffmann
2016-01-07 14:36 ` Sergio Gonzalez Monroy
2016-01-07 14:54 ` [dpdk-dev] [PATCH v5 1/1] eal/linux: " Ralf Hoffmann
2016-03-02 16:13 ` Thomas Monjalon
2015-09-09 8:41 ` [dpdk-dev] [PATCH v1] " Ralf Hoffmann
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=1451985913-16235-1-git-send-email-ralf.hoffmann@allegro-packets.com \
--to=ralf.hoffmann@allegro-packets.com \
--cc=dev@dpdk.org \
--cc=sergio.gonzalez.monroy@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).