From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Pawel Wodkowski <pawelx.wodkowski@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: fix '--huge-unlink' option
Date: Fri, 5 Oct 2018 09:13:06 +0100 [thread overview]
Message-ID: <2b5aab7e-85cc-eb44-7da8-1bdc7484f298@intel.com> (raw)
In-Reply-To: <1537530998-109749-1-git-send-email-pawelx.wodkowski@intel.com>
On 21-Sep-18 12:56 PM, Pawel Wodkowski wrote:
> The final_va field is set during remap_segment() but this information is
> not propagated to temporal copy of huge page memory configuration so the
> unlink_hugepage_files() function wrongly assume that there is nothing to
> unlink. Fix this issue by checking orig_va instead of final_va.
>
> Fixes: 66cc45e293ed ("mem: replace memseg with memseg lists")
> To: Anatoly Burakov <anatoly.burakov@intel.com>
>
> Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-10-05 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 11:56 Pawel Wodkowski
2018-09-21 8:31 ` Stojaczyk, Dariusz
2018-09-26 18:12 ` Wodkowski, PawelX
2018-10-05 8:13 ` Burakov, Anatoly [this message]
2018-10-11 9:40 ` 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=2b5aab7e-85cc-eb44-7da8-1bdc7484f298@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=pawelx.wodkowski@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).