Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262653AbUCJPTy (ORCPT ); Wed, 10 Mar 2004 10:19:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262655AbUCJPTy (ORCPT ); Wed, 10 Mar 2004 10:19:54 -0500 Received: from [217.157.19.70] ([217.157.19.70]:13321 "EHLO jehova.dsm.dk") by vger.kernel.org with ESMTP id S262653AbUCJPTw (ORCPT ); Wed, 10 Mar 2004 10:19:52 -0500 Date: Wed, 10 Mar 2004 15:19:50 +0000 (GMT) From: Thomas Horsten X-X-Sender: thomas@jehova.dsm.dk To: Bartlomiej Zolnierkiewicz cc: andre@linux-ide.org, , Subject: Re: [PATCH] 2.4.x Linux Medley RAID Version 7 In-Reply-To: <200403101539.28258.bzolnier@elka.pw.edu.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1219 Lines: 30 On Wed, 10 Mar 2004, Bartlomiej Zolnierkiewicz wrote: > I don't like the idea of having 2 drivers doing basically the same thing. > Please explain why we can't have one Medley software RAID driver? > [ Yes, I read http://www.ussg.iu.edu/hypermail/linux/kernel/0308.0/0156.html ] The existing one does not work correctly: - It detects the array in the wrong way and so only catches a fraction of valid Medley sets (and possibly mistakes non-Medley sets or deleted sets for correct ones). - It's using the wrong algorithm for dealing with striped arrays where the drives are of different sizes. The reason my patch leaves it in place is that it works for some users, and some people pointed out last year that the usual preferred path for this kind of change is to leave the existing driver in place if it works for some people. I would personally prefer to remove it. Andre has previously stated that he had no objections to this patch (an earlier version). // Thomas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/