From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Michael Santana <msantana@redhat.com>, dev <dev@dpdk.org>,
Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
Subject: Re: [dpdk-dev] Hugepages not being deleted
Date: Mon, 20 May 2019 12:45:21 +0100 [thread overview]
Message-ID: <74a685f7-a33c-628e-9f1b-f79d2db207d4@intel.com> (raw)
In-Reply-To: <CAJFAV8zf7S2ii8_4HbVyJczKG9ocfAPXh0gPvOwVqj7ez6JZMQ@mail.gmail.com>
On 20-May-19 12:09 PM, David Marchand wrote:
> On Mon, May 20, 2019 at 12:43 PM Burakov, Anatoly
> <anatoly.burakov@intel.com <mailto:anatoly.burakov@intel.com>> wrote:
>
> On 17-May-19 3:06 PM, David Marchand wrote:
> > Hello Anatoly,
> >
> > Not sure what the issue is at the moment.
> > I too have an error on the eal_flags_autotest but what is
> worrying me is
> > that it works fine in 18.11.1 and 19.02.
> > Is there anything that rings a bell?
> >
> > Thanks.
> >
> > --
> > David Marchand
>
> Not to me. Last i checked they were passing.
>
>
> Bisected it, I will send a fix.
>
>
> --
> David Marchand
I've bisected it too. I think Erik (author of original patch) already is
working on the problem. I don't think it's easily (and safely) solvable.
You can find more info in below threads:
http://patches.dpdk.org/patch/53191/
http://patches.dpdk.org/patch/53268/
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-05-20 11:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 15:15 Michael Santana Francisco
2019-04-23 15:15 ` Michael Santana Francisco
2019-04-29 18:28 ` Michael Santana Francisco
2019-04-29 18:28 ` Michael Santana Francisco
2019-04-30 9:32 ` Burakov, Anatoly
2019-04-30 9:32 ` Burakov, Anatoly
2019-05-17 14:06 ` David Marchand
2019-05-20 10:43 ` Burakov, Anatoly
2019-05-20 11:09 ` David Marchand
2019-05-20 11:45 ` Burakov, Anatoly [this message]
2019-05-20 11:48 ` David Marchand
2019-05-20 15:08 ` Carrillo, Erik G
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=74a685f7-a33c-628e-9f1b-f79d2db207d4@intel.com \
--to=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=msantana@redhat.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).