Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp341669pxb; Tue, 3 Nov 2020 00:34:57 -0800 (PST) X-Google-Smtp-Source: ABdhPJwi5JbvHP8ntdns3Sq2MmqLhq2uBaS/EDfnQLGW4xYLK5+Ovi9KjXiFYeKeeHnjYwz53QTG X-Received: by 2002:a05:6402:1c04:: with SMTP id ck4mr20989954edb.274.1604392497038; Tue, 03 Nov 2020 00:34:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1604392497; cv=none; d=google.com; s=arc-20160816; b=PAtcGwu+QrmwN7M/Y/29b0gaJCE6PwMzQFhuJkn/gLooyjex4KemDsmpwA1cOBewnL B5GxcyHQ650f6utOz0zrCg5MZ/ZYotWb1v+L3ovE5ViOy97jjJXTjc478H8OvxtaA0Zc iK4NGigEVBmAlbBZ2AZLMfpo5oLXdVsd3XYjRtYskv4Zo48yASEJcpP1mo0CwFsnG8QX TKEhrOb3iNVXZGX+kjKApMasTX1SP+nAxFjtYB+jt9gjxeU5nk3WKIf6H7swBX/lTx3F bLgMc40oD2yVJaW+IyS+Ku5JY8WI+oOdoYLl3KtcTYrQN+IscqYw+Jrq8RVAtY3fOgfy y04w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=0AVrrnFk2LK6xv5QQDL/L5IslzwzGSKzr0bCkym7Zn8=; b=Fi1+qMbKQebvZX21D129ie649a91KrKZYqnOCzNt+Pa+xLJff6+W2tzgIowZS+qXAW fGivVlU3c/I72YEqeeEB3c6lj+DfZOii9lMLENrMvqhIzhD7mX3EzHSH62z/mk97ES5k q+mPzZeav1xcu5eU65P2HyCoxjY6qBmPPy4VbDoh0GjJS5VsCI66dj8nZBuM4+3GbE9h FXdaMGk7D/ldoFpp7n8gTTGTUhgf6fb22g9VT81MFyaP+Ds2VedJElw9hDTjvU8t61zM BU/Vxz0n1LF+SMmMIK3VSjHd4LcLoZRna/0jCTZgxcnK4okLGCMPtpZQb2xvi1hoX55w 1Zvw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Eq5l+fd+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d4si12223747edr.173.2020.11.03.00.34.34; Tue, 03 Nov 2020 00:34:57 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Eq5l+fd+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727239AbgKCIcr (ORCPT + 99 others); Tue, 3 Nov 2020 03:32:47 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:23971 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725982AbgKCIcq (ORCPT ); Tue, 3 Nov 2020 03:32:46 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1604392365; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=0AVrrnFk2LK6xv5QQDL/L5IslzwzGSKzr0bCkym7Zn8=; b=Eq5l+fd+VKF6HkfsP/HWOmzC/VRokebi+TMHAhFuJOPRPnxdkXObT5BhTVNalFgGM5XAzc o5kkbogs6o3gqb4kdnCsDp9Qis4l6tM2zrt+IToQf8Zq7HRCPod0zr3qwaClTwvSEtLrzz STaRzHtfm50lw+4pupKqgkXB8xfWG9M= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-358-msbyy7JzMaanGxALteOV5Q-1; Tue, 03 Nov 2020 03:32:43 -0500 X-MC-Unique: msbyy7JzMaanGxALteOV5Q-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id AAF5E8030C4; Tue, 3 Nov 2020 08:32:42 +0000 (UTC) Received: from localhost.localdomain (ovpn-8-30.pek2.redhat.com [10.72.8.30]) by smtp.corp.redhat.com (Postfix) with ESMTP id 0C21E5C5DE; Tue, 3 Nov 2020 08:32:39 +0000 (UTC) Subject: Re: [PATCH 0/3] mdraid sb and bitmap write alignment on 512e drives To: Chris Unkel Cc: linux-raid , open list , Song Liu References: <20201023033130.11354-1-cunkel@drivescale.com> From: Xiao Ni Message-ID: Date: Tue, 3 Nov 2020 16:32:37 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/03/2020 02:59 AM, Chris Unkel wrote: > Hi Xiao, > > That particular array is super1.2. The block trace was captured on > the disk underlying the partition device on which the md array member > resides, not on the partition device itself. The partition starts > 2048 sectors into the disk (1MB). So the 2048 sectors offset to the > beginning of the partition, plus the 8 sector superblock offset for > super1.2 ends up at 2056. > > Sorry for the confusion there. > > Regards, > > --Chris Thanks for the explanation. I still have some questions in other emails about your patch. Could you have a look when you are free. Regards Xiao