From: Eric Hagberg <ehagberg@janestreet.com>
To: christoph.boehmwalder@linbit.com
Cc: axboe@kernel.dk, philipp.reisner@linbit.com,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Eric Hagberg <ehagberg@janestreet.com>,
lars.ellenberg@linbit.com, drbd-dev@lists.linbit.com
Subject: [PATCH] drbd: Remove the open-coded page pool
Date: Mon, 11 Aug 2025 09:16:02 -0400 [thread overview]
Message-ID: <20250811131602.978555-1-ehagberg@janestreet.com> (raw)
In-Reply-To: <20250605103852.23029-1-christoph.boehmwalder@linbit.com>
This patch has ben running on thousands of hosts here and we've not seen the memory leak that
was happening previously.
Tested-by: Eric Hagberg <ehagberg@janestreet.com>
next prev parent reply other threads:[~2025-08-11 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 10:38 [PATCH] drbd: Remove the open-coded page pool Christoph Böhmwalder
2025-08-11 13:16 ` Eric Hagberg [this message]
2025-08-11 14:01 ` Jens Axboe
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=20250811131602.978555-1-ehagberg@janestreet.com \
--to=ehagberg@janestreet.com \
--cc=axboe@kernel.dk \
--cc=christoph.boehmwalder@linbit.com \
--cc=drbd-dev@lists.linbit.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.reisner@linbit.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