[PATCH 00/20] DRBD 9 rework

[Jens Axboe]

On 4/9/26 12:40 AM, Christoph Hellwig wrote:
> First an apology, I thought it was in your tree, but it looks like
> the drbd branch just has minor fixes.  So a lot less urgency.

No worries, figured you hadn't seen the previous discussion.

> On Wed, Apr 08, 2026 at 06:58:58AM -0600, Jens Axboe wrote:
>> See the previous discussion,
> 
> Do you have a pointer to that discussion?  I can't remember one.

I'm on pretty poor connectivity right now, but find some of my complaining
on linux-block in response to a previous Christian email.

>> the goal is to sync the two drbd code
>> bases. It's followed the "usual" pattern of the in-kernel driver being
>> neglected and development and users pushed to the out-of-tree one,
>> which is highly annoying.
> 
> I don't think that's a a usual pattern.  Also the new version looks
> like a complete rewrite and not something incremental:
> 
>  45 files changed, 45891 insertions(+), 16264 deletions(-)
> 
> For a code base that is "29482 total".
> 
> I think reviewing it would be easier by just adding an new drbd9 driver
> and then steering people toward it carefully, as that is actually
> reviewable compared to non-bisectable patches changing large chunks
> of code in a non-atomic way.

That is another approach we could take, but I don't think that would
make it any easier to review, to be honest. Nobody reviews a full
driver, their eyes just kind of gloss over.

Heads up - OOO for 1 week, will prep merge window stuff to the best
of my abilities, but won't be super responsive outside of that. As
this particular driver isn't going anywhere right now, there's no
urgency on that side of things.

-- 
Jens Axboe