linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Keith Busch <kbusch@meta.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] dmapool: push new blocks in ascending order
Date: Tue, 21 Feb 2023 17:20:10 +0000	[thread overview]
Message-ID: <78dfd8ec-967e-2bd2-9b8c-b7338ed62049@linaro.org> (raw)
In-Reply-To: <20230221165400.1595247-1-kbusch@meta.com>

On 21/02/2023 16:54, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
> 
> Some users of the dmapool need their allocations to happen in ascending
> order. The recent optimizations pushed the blocks in reverse order, so
> restore the previous behavior by linking the next available block from
> low-to-high.
> 
> Fixes: ced6d06a81fb69 ("dmapool: link blocks across pages")
> Reported-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> Signed-off-by: Keith Busch <kbusch@kernel.org>

Tested-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>



  reply	other threads:[~2023-02-21 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 16:54 [PATCH] dmapool: push new blocks in ascending order Keith Busch
2023-02-21 17:20 ` Bryan O'Donoghue [this message]
2023-02-21 18:02 ` Christoph Hellwig
2023-02-21 18:07   ` Keith Busch
2023-02-23 20:41     ` Andrew Morton
2023-02-24 18:24       ` Keith Busch
2023-02-24 22:28         ` Bryan O'Donoghue
2023-02-26  4:42 ` Andrew Morton
2023-02-27 17:20   ` Keith Busch
2023-02-28  1:25   ` Keith Busch
2023-02-28  2:14 ` Guenter Roeck

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=78dfd8ec-967e-2bd2-9b8c-b7338ed62049@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=kbusch@kernel.org \
    --cc=kbusch@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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).