From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9060BC388F9 for ; Wed, 21 Oct 2020 11:15:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1419521655 for ; Wed, 21 Oct 2020 11:15:17 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=veeam.com header.i=@veeam.com header.b="J7l2nPmP" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2441927AbgJULPM (ORCPT ); Wed, 21 Oct 2020 07:15:12 -0400 Received: from mx4.veeam.com ([104.41.138.86]:43548 "EHLO mx4.veeam.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2410622AbgJULPJ (ORCPT ); Wed, 21 Oct 2020 07:15:09 -0400 Received: from mail.veeam.com (spbmbx01.amust.local [172.17.17.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx4.veeam.com (Postfix) with ESMTPS id EABE6897F6; Wed, 21 Oct 2020 14:15:04 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=veeam.com; s=mx4; t=1603278905; bh=N8h1eQSrAq99HPEtyM6BB2zVpJlELnewpRvhCbmIWg8=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=J7l2nPmPgQ3+NtzyjsDswFT4EL2ccUF1DN0D2J1KfzxygUgBbVhHcK0KiRQ8Q+V/6 KC/Pd96uBtdio9IQNueanRxv1rESVaecIkV8l8ImrZxq+xWWmB4broU3y45Ul5S82q K2EBYYbfSJz43xB9cYDQtHeEo0RBMQiavsVAv00Q= Received: from veeam.com (172.24.14.5) by spbmbx01.amust.local (172.17.17.171) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.595.3; Wed, 21 Oct 2020 14:15:02 +0300 Date: Wed, 21 Oct 2020 14:15:51 +0300 From: Sergei Shtepa To: Damien Le Moal CC: "axboe@kernel.dk" , "viro@zeniv.linux.org.uk" , "hch@infradead.org" , "darrick.wong@oracle.com" , "linux-xfs@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , "rjw@rjwysocki.net" , "len.brown@intel.com" , "pavel@ucw.cz" , "akpm@linux-foundation.org" , Johannes Thumshirn , "ming.lei@redhat.com" , "jack@suse.cz" , "tj@kernel.org" , "gustavo@embeddedor.com" , "bvanassche@acm.org" , "osandov@fb.com" , "koct9i@gmail.com" , "steve@sk2.org" , "linux-block@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-pm@vger.kernel.org" , "linux-mm@kvack.org" Subject: Re: [PATCH 2/2] blk-snap - snapshots and change-tracking for block devices Message-ID: <20201021111551.GD20749@veeam.com> References: <1603271049-20681-1-git-send-email-sergei.shtepa@veeam.com> <1603271049-20681-3-git-send-email-sergei.shtepa@veeam.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline In-Reply-To: X-Originating-IP: [172.24.14.5] X-ClientProxiedBy: spbmbx02.amust.local (172.17.17.172) To spbmbx01.amust.local (172.17.17.171) X-EsetResult: clean, is OK X-EsetId: 37303A295605D26A677560 X-Veeam-MMEX: True Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org > And this is a 8600+ lines patch. > Can you split this into manageable pieces ? Yes, the module was quite large. But I think it's not good to show the elephant in parts. https://en.wikipedia.org/wiki/Blind_men_and_an_elephant > I do not think anybody will review such a huge patch. Yes, it will be a lot of work. But I hope that the code architecture and splitting entities into separate files will help. If someone can advise how to divide a module into a chain of patches, I will be happy. I do not dare to divide it without losing meaning. -- Sergei Shtepa Veeam Software developer.