From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752615AbbIQS2Z (ORCPT ); Thu, 17 Sep 2015 14:28:25 -0400 Received: from mail.cmpwn.com ([45.56.77.53]:37319 "EHLO mail.cmpwn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751785AbbIQS2Y (ORCPT ); Thu, 17 Sep 2015 14:28:24 -0400 Subject: Re: Failover root devices To: Richard Weinberger References: <55FAA6BB.3060008@odi.ch> <20150917114955.GA2600@homura> <55FAFD1D.8030305@cmpwn.com> <55FAFDE1.2020707@nod.at> <55FB00E6.3090801@cmpwn.com> <55FB03B8.2000101@nod.at> <55FB03E8.3000604@cmpwn.com> <55FB0441.6040709@nod.at> <55FB0498.9060301@cmpwn.com> <55FB0531.3050006@nod.at> Cc: =?UTF-8?Q?Ortwin_Gl=c3=bcck?= , "linux-kernel@vger.kernel.org" From: Drew DeVault Message-ID: <55FB0646.1020704@cmpwn.com> Date: Thu, 17 Sep 2015 14:28:22 -0400 MIME-Version: 1.0 In-Reply-To: <55FB0531.3050006@nod.at> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > The kernel is already super complicated and has millions of lines of code. If it can be done nicely in userspace, let's do it there > and keep the kernel maintainable. I don't think this is a strong argument against this feature. The implementation of this feature will be pretty straightfoward - only a small part of the code has to actually change its behavior and it can do without changing the interfaces it already relies on. On top of that, I don't think it can be done "nicely" in userspace anyway. -- Drew DeVault