From: Andrew Morton <akpm@linux-foundation.org>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Rick Edgecombe <rick.p.edgecombe@intel.com>
Subject: Re: [PATCH v2] mm/mmap: Regression fix for unmapped_area{_topdown}
Date: Fri, 14 Apr 2023 12:09:57 -0700 [thread overview]
Message-ID: <20230414120957.d69f471ad9eb2a1d304a4146@linux-foundation.org> (raw)
In-Reply-To: <20230414185919.4175572-1-Liam.Howlett@oracle.com>
On Fri, 14 Apr 2023 14:59:19 -0400 "Liam R. Howlett" <Liam.Howlett@oracle.com> wrote:
> The maple tree limits the gap returned to a window that specifically
> fits what was asked. This may not be optimal in the case of switching
> search directions or a gap that does not satisfy the requested space for
> other reasons. Fix the search by retrying the operation and limiting
> the search window in the rare occasion that a conflict occurs.
This is a performance regression, yes? Of what magnitude?
next prev parent reply other threads:[~2023-04-14 19:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 14:57 [PATCH 1/3] maple_tree: Make maple state reusable after mas_empty_area_rev() Liam R. Howlett
2023-04-14 14:57 ` [PATCH 2/3] maple_tree: Fix mas_empty_area() search Liam R. Howlett
2023-04-14 14:57 ` [PATCH 3/3] mm/mmap: Regression fix for unmapped_area{_topdown} Liam R. Howlett
2023-04-14 16:27 ` Edgecombe, Rick P
2023-04-14 17:26 ` Liam R. Howlett
2023-04-14 17:29 ` Liam R. Howlett
2023-04-14 17:53 ` Edgecombe, Rick P
2023-04-14 18:07 ` Liam R. Howlett
2023-04-14 18:21 ` Edgecombe, Rick P
2023-04-14 18:59 ` [PATCH v2] " Liam R. Howlett
2023-04-14 19:09 ` Andrew Morton [this message]
2023-04-29 14:32 ` Tad
2023-04-30 22:41 ` Michael Keyes
2023-05-02 14:08 ` Liam R. Howlett
2023-05-02 14:09 ` Liam R. Howlett
2023-05-15 8:57 ` Juhyung Park
2023-05-15 14:36 ` Liam R. Howlett
2023-04-19 9:02 ` [PATCH 1/3] maple_tree: Make maple state reusable after mas_empty_area_rev() Peng Zhang
2023-04-19 22:54 ` Liam R. Howlett
2023-04-20 4:21 ` Peng Zhang
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=20230414120957.d69f471ad9eb2a1d304a4146@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rick.p.edgecombe@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