From: Jens Axboe <axboe@kernel.dk>
To: Philipp Reisner <philipp.reisner@linbit.com>
Cc: Christoph Hellwig <hch@lst.de>,
Lars Ellenberg <lars.ellenberg@linbit.com>,
drbd-dev@lists.linbit.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: state of drbd in mainline
Date: Tue, 29 Mar 2022 09:52:07 -0600 [thread overview]
Message-ID: <3c42b1ed-7c03-64e6-409e-e92247288cac@kernel.dk> (raw)
In-Reply-To: <CADGDV=WN2TFR6dO7ZdiQ2ijPjs+7HSsvk0ZCHsHj6ZG5t-oEdA@mail.gmail.com>
On 3/29/22 9:44 AM, Philipp Reisner wrote:
> Jens, my intention is to keep it in-tree, and at some point update it.
> Regarding your questions:
That'd be great, but it's been years since there was any significant
updates to the in-kernel drbd... I would strongly suggest that the
in-kernel be brought closer to what people are mostly running, as it
stands it's basically unmaintained.
>> - Why aren't the drbd maintainers responding to posted patches? They seem
>> to simply be ignored, and I'm left to pickup the trivial ones that look
>> fine to me. In-kernel drbd appears largely unmaintained, and has been for
>> years.
>
> The team here has grown, we are busy. Since you started to pick up the
> trivial patches yourself, I thought it is not necessary that I collect
> them and send a pull request in merge-window time.
That's just one part of it, the fact that the out-of-tree drbd has been
drifting further and further away from the in-kernel one is a big
problem. For trivial patches, I have no issue picking them up. But
silence on your side is not very helpful. Please review and ack patches.
If I see it acked, then I can easily pick it up.
>> - Even if out-of-band communication is used for in-kernel users of drbd,
>> that doesn't result in any patches or fixes that should go upstream?
>
> This one:
> https://patchwork.kernel.org/project/linux-block/patch/20210426163032.3454129-1-christoph.boehmwalder@linbit.com/
> (relevant to users that have DRBD on top of md raid)
That's a single patch, from a year ago. Not a strong counter point,
looks more like it's proving my case...
>> - If there's zero activity for in-kernel drbd, all users are using the
>> out-of-tree version?
>
> There are users of the in-tree version, some with huge fleets.
> Some do not need the newer out-of-tree DRBD, and the in-tree version is a
> lot easier to compile. You need coccinelle for the out-of-tree version,
> and that can already be a hindering barrier for some.
The main discrepancy here is that there are apparently huge numbers of
in-tree users, yet no fixes or patches at all making it to mainline.
Either drbd is bug free and doesn't require any fixes at all, which I
very much would doubt, or fixes aren't being sent upstream.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Philipp Reisner <philipp.reisner@linbit.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Lars Ellenberg <lars.ellenberg@linbit.com>,
Christoph Hellwig <hch@lst.de>,
drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] state of drbd in mainline
Date: Tue, 29 Mar 2022 09:52:07 -0600 [thread overview]
Message-ID: <3c42b1ed-7c03-64e6-409e-e92247288cac@kernel.dk> (raw)
In-Reply-To: <CADGDV=WN2TFR6dO7ZdiQ2ijPjs+7HSsvk0ZCHsHj6ZG5t-oEdA@mail.gmail.com>
On 3/29/22 9:44 AM, Philipp Reisner wrote:
> Jens, my intention is to keep it in-tree, and at some point update it.
> Regarding your questions:
That'd be great, but it's been years since there was any significant
updates to the in-kernel drbd... I would strongly suggest that the
in-kernel be brought closer to what people are mostly running, as it
stands it's basically unmaintained.
>> - Why aren't the drbd maintainers responding to posted patches? They seem
>> to simply be ignored, and I'm left to pickup the trivial ones that look
>> fine to me. In-kernel drbd appears largely unmaintained, and has been for
>> years.
>
> The team here has grown, we are busy. Since you started to pick up the
> trivial patches yourself, I thought it is not necessary that I collect
> them and send a pull request in merge-window time.
That's just one part of it, the fact that the out-of-tree drbd has been
drifting further and further away from the in-kernel one is a big
problem. For trivial patches, I have no issue picking them up. But
silence on your side is not very helpful. Please review and ack patches.
If I see it acked, then I can easily pick it up.
>> - Even if out-of-band communication is used for in-kernel users of drbd,
>> that doesn't result in any patches or fixes that should go upstream?
>
> This one:
> https://patchwork.kernel.org/project/linux-block/patch/20210426163032.3454129-1-christoph.boehmwalder@linbit.com/
> (relevant to users that have DRBD on top of md raid)
That's a single patch, from a year ago. Not a strong counter point,
looks more like it's proving my case...
>> - If there's zero activity for in-kernel drbd, all users are using the
>> out-of-tree version?
>
> There are users of the in-tree version, some with huge fleets.
> Some do not need the newer out-of-tree DRBD, and the in-tree version is a
> lot easier to compile. You need coccinelle for the out-of-tree version,
> and that can already be a hindering barrier for some.
The main discrepancy here is that there are apparently huge numbers of
in-tree users, yet no fixes or patches at all making it to mainline.
Either drbd is bug free and doesn't require any fixes at all, which I
very much would doubt, or fixes aren't being sent upstream.
--
Jens Axboe
next prev parent reply other threads:[~2022-03-29 15:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 7:06 state of drbd in mainline Christoph Hellwig
2022-03-29 7:06 ` [Drbd-dev] " Christoph Hellwig
2022-03-29 7:22 ` Philipp Reisner
2022-03-29 7:32 ` Christoph Hellwig
2022-03-29 7:32 ` [Drbd-dev] " Christoph Hellwig
2022-03-29 7:50 ` Philipp Reisner
2022-03-29 7:50 ` [Drbd-dev] " Philipp Reisner
2022-03-29 12:29 ` Jens Axboe
2022-03-29 12:29 ` [Drbd-dev] " Jens Axboe
2022-03-29 15:44 ` Philipp Reisner
2022-03-29 15:44 ` [Drbd-dev] " Philipp Reisner
2022-03-29 15:52 ` Jens Axboe [this message]
2022-03-29 15:52 ` Jens Axboe
2022-03-30 15:23 ` Philipp Reisner
2022-03-30 15:23 ` [Drbd-dev] " Philipp Reisner
2022-03-30 18:06 ` Mike Snitzer
2022-03-30 18:06 ` [Drbd-dev] " Mike Snitzer
2022-03-30 18:24 ` Jens Axboe
2022-03-30 18:24 ` [Drbd-dev] " Jens Axboe
2022-03-30 19:31 ` Kiselev, Oleg
2022-03-30 19:31 ` Kiselev, Oleg
2022-03-30 20:21 ` Jens Axboe
2022-03-30 20:21 ` Jens Axboe
2022-03-29 20:01 ` Wolfgang Walter
2022-03-29 20:01 ` Wolfgang Walter
2022-03-29 7:24 ` Philipp Reisner
2022-03-29 7:24 ` [Drbd-dev] " Philipp Reisner
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=3c42b1ed-7c03-64e6-409e-e92247288cac@kernel.dk \
--to=axboe@kernel.dk \
--cc=drbd-dev@lists.linbit.com \
--cc=hch@lst.de \
--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 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.