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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2EA25C433F5 for ; Fri, 11 Mar 2022 07:34:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233325AbiCKHfn (ORCPT ); Fri, 11 Mar 2022 02:35:43 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35388 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241115AbiCKHfm (ORCPT ); Fri, 11 Mar 2022 02:35:42 -0500 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7B7FA1B71BD for ; Thu, 10 Mar 2022 23:34:40 -0800 (PST) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 001A1218FC for ; Fri, 11 Mar 2022 07:34:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1646984079; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc: mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=Mh7XEvssiy9UBPRpL5xvE47lun6/EAt4hg2vpseV4wc=; b=SncTEwc51Q6lx/ytAoWc8qvEWV8o63A24+AILuMexIVPKpK33ccDeZNtvd+p2RlrpqaS18 Awoegw95No3/omnSwM8BlpsfhGcrbahYhBoCBxhFwPjrie5DE34YKtxjgitSCu2pj4orl1 HeJqYZ0PfihEJZtqk7ylOoh8IipJUA4= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 46D4413A82 for ; Fri, 11 Mar 2022 07:34:38 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id Z2Z+A477KmIrJQAAMHmgww (envelope-from ) for ; Fri, 11 Mar 2022 07:34:38 +0000 From: Qu Wenruo To: linux-btrfs@vger.kernel.org Subject: [PATCH v2 0/3] btrfs: scrub: big renaming to address the page and sector difference Date: Fri, 11 Mar 2022 15:34:17 +0800 Message-Id: X-Mailer: git-send-email 2.35.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org This patchset can be cherry-picked from my github repo: https://github.com/adam900710/linux/tree/refactor_scrub They are the first 3 patches after misc-next. >From the ancient day, btrfs doesn't support sectorsize < PAGE_SIZE, thus a lot of the old code consider one page == one sector, not only the behavior, but also the naming. This is no longer true after v5.16 since we have subpage support. One of the worst location is scrub, we have tons of things named like scrub_page, scrub_block::pagev, scrub_bio::pagev. Even scrub for subpage is supported, the naming is not touched yet. This patchset will first do the rename, providing the basis for later scrub enhancement for subpage. This patchset should not bring any behavior change. Changelog: v2: - Rebased to misc-next directly, before scrub entrance refactor As this patchset is safer than entrance refactor. Minor conflicts due to scrub_remap() renaming. Qu Wenruo (3): btrfs: scrub: rename members related to scrub_block::pagev btrfs: scrub: rename scrub_page to scrub_sector btrfs: scrub: rename scrub_bio::pagev and related members fs/btrfs/scrub.c | 688 +++++++++++++++++++++++------------------------ 1 file changed, 344 insertions(+), 344 deletions(-) -- 2.35.1