From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Remy Horton <remy.horton@intel.com>, dev@dpdk.org
Cc: sergio.gonzalez.monroy@intel.com
Subject: Re: [PATCH v3 3/3] memzone: improve zero-length memzone reserve
Date: Tue, 15 May 2018 09:37:53 +0100 [thread overview]
Message-ID: <33e5ba67-59cc-46e1-fe26-0fed53abaf83@intel.com> (raw)
In-Reply-To: <147e5200-1a7a-017a-2428-7813ead41ff5@intel.com>
On 15-May-18 7:24 AM, Remy Horton wrote:
>
> On 14/05/2018 12:29, Burakov, Anatoly wrote:
> [..]
>> This failure is not caused by this patchset, and you should get similar
>> failures on master if you get these while testing my patchset. I am not
>> able to reproduce this issue, but i'll double-check the bounded reserve
>> code with a fine-toothed comb anyway.
>
> I reliably get the failure with V3 applied to RC2, but so far haven't
> been able to replicate with any other combination (clean RC2, RC2+V5,
> master+V4, etc). Odd..
>
I've retested on plain v3+rc2 (i was previously testing on master), and
i can reproduce the failure as well. The bug that was causing this issue
was fixed on rebase in v4. So, rc2+v4/v5 no longer has this issue.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-05-15 8:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 14:10 [PATCH 1/2] malloc: add biggest free IOVA-contiguous element to stats Anatoly Burakov
2018-04-25 14:10 ` [PATCH 2/2] memzone: allow IOVA-contiguous memzones with zero size Anatoly Burakov
2018-04-25 14:40 ` [PATCH 1/2] malloc: add biggest free IOVA-contiguous element to stats Burakov, Anatoly
2018-04-26 8:06 ` [PATCH v2 " Anatoly Burakov
2018-05-03 17:17 ` [PATCH v3 0/3] Improve zero-length memzone allocation Anatoly Burakov
2018-05-03 17:17 ` [PATCH v3 1/3] malloc: add biggest free IOVA-contiguous element to stats Anatoly Burakov
2018-05-10 13:39 ` Remy Horton
2018-05-03 17:18 ` [PATCH v3 2/3] malloc: allow reserving biggest element Anatoly Burakov
2018-05-10 13:57 ` Remy Horton
2018-05-14 8:22 ` Burakov, Anatoly
2018-05-03 17:18 ` [PATCH v3 3/3] memzone: improve zero-length memzone reserve Anatoly Burakov
2018-05-11 10:25 ` Remy Horton
2018-05-14 8:21 ` Burakov, Anatoly
2018-05-14 11:29 ` Burakov, Anatoly
2018-05-14 12:23 ` Burakov, Anatoly
2018-05-15 6:24 ` Remy Horton
2018-05-15 8:37 ` Burakov, Anatoly [this message]
2018-05-14 11:19 ` [PATCH v4 0/3] Improve zero-length memzone allocation Anatoly Burakov
2018-05-14 11:19 ` [PATCH v4 1/3] malloc: add biggest free IOVA-contiguous element to stats Anatoly Burakov
2018-05-14 11:19 ` [PATCH v4 2/3] malloc: allow reserving biggest element Anatoly Burakov
2018-05-14 11:19 ` [PATCH v4 3/3] memzone: improve zero-length memzone reserve Anatoly Burakov
2018-05-14 13:47 ` [PATCH v5 0/3] Improve zero-length memzone allocation Anatoly Burakov
2018-05-14 13:47 ` [PATCH v5 1/3] malloc: add biggest free IOVA-contiguous element to stats Anatoly Burakov
2018-05-14 13:58 ` Shreyansh Jain
2018-05-14 13:47 ` [PATCH v5 2/3] malloc: allow reserving biggest element Anatoly Burakov
2018-05-14 13:47 ` [PATCH v5 3/3] memzone: improve zero-length memzone reserve Anatoly Burakov
2018-05-31 9:50 ` [PATCH v6 0/3] Improve zero-length memzone allocation Anatoly Burakov
2018-05-31 9:50 ` [PATCH v6 1/3] malloc: add finding biggest free IOVA-contiguous element Anatoly Burakov
2018-05-31 9:51 ` [PATCH v6 2/3] malloc: allow reserving biggest element Anatoly Burakov
2018-05-31 9:51 ` [PATCH v6 3/3] memzone: improve zero-length memzone reserve Anatoly Burakov
2018-07-13 9:24 ` [PATCH v6 0/3] Improve zero-length memzone allocation Thomas Monjalon
2018-04-26 8:06 ` [PATCH v2 2/2] memzone: allow IOVA-contiguous memzones with zero size Anatoly Burakov
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=33e5ba67-59cc-46e1-fe26-0fed53abaf83@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=remy.horton@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.