[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CADGDV=XrhzSxLyES9dtKj1-cQq6Zh32psipLJCoDGRNzAYaZwA@mail.gmail.com>
Date: Tue, 29 Mar 2022 09:24:33 +0200
From: Philipp Reisner <philipp.reisner@...bit.com>
To: Christoph Hellwig <hch@....de>
Cc: Lars Ellenberg <lars.ellenberg@...bit.com>,
Jens Axboe <axboe@...nel.dk>, drbd-dev@...ts.linbit.com,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: state of drbd in mainline
Hi Christoph,
what do you expect for the DRBD changes? Usually, they fall into the
category: yes, obviously. When you are changing the block layer in
this way, then that is necessary for the in-tree DRBD code.
Regarding users: Yes, there are users of the in-tree DRBD code. Very
big corporations. And, yes, we see pressure building up that we get
our act together and re-sync the in-tree DRBD with the out-of tree
DRBD.
best regards,
Phil
On Tue, Mar 29, 2022 at 9:06 AM Christoph Hellwig <hch@....de> wrote:
>
> Hi all,
>
> while I've been reworking large parts of the block layer over the
> last months I've basically never gotten drbd reviews, and in general
> drbd seems to be completely maintained upstream. Do we even have users
> for it? Is it time to drop drbd from the kernel tree?
>
> Thanks,
> Christoph
Powered by blists - more mailing lists