From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2B4DD79E1; Mon, 23 Sep 2024 03:33:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.95.11.211 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1727062395; cv=none; b=AD4ao4/z6IWj6sBkcXadRtg9Zt17eiM1XZXyVV8N3+EzUMfaLTUxzNiz2qLI5lItHCY+6tfmgy1qMiU14PXnABeSQpOcSvRY7chskiKKO0ltT8OY+srB0IWOD/K/5GP96ai8L/4bf18h4Sdt4lq7r2b8RoRlfXasfaGaUVkIxe8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1727062395; c=relaxed/simple; bh=KIuSXjpzAJGxS/ob+rdaP1ri1Y42g4YaGiFmdFfD078=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=jJOTADBV4TPSSPUvvatwdQCvrYXOosC8xs9dbtA1CAvUxStoWefQYavUybtch0PVefTdlMjf2MvMYI0ZOB7PkaqvaPvcxpp+jaqOGsUh49e9/zHDK4dxq3/hE5pNrBQGYbO8Uwf8tHLMf1rlvY72MzQlHznbp7sC6WronDWgRWc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de; spf=pass smtp.mailfrom=lst.de; arc=none smtp.client-ip=213.95.11.211 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lst.de Received: by verein.lst.de (Postfix, from userid 2407) id 3FCF6227AAF; Mon, 23 Sep 2024 05:33:06 +0200 (CEST) Date: Mon, 23 Sep 2024 05:33:05 +0200 From: Christoph Hellwig To: Dave Chinner Cc: John Garry , Ritesh Harjani , chandan.babu@oracle.com, djwong@kernel.org, dchinner@redhat.com, hch@lst.de, viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz, linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, catherine.hoang@oracle.com, martin.petersen@oracle.com Subject: Re: [PATCH v4 00/14] forcealign for xfs Message-ID: <20240923033305.GA30200@lst.de> References: <87frqf2smy.fsf@gmail.com> <877cbq3g9i.fsf@gmail.com> <8734m7henr.fsf@gmail.com> <8e13fa74-f8f7-49d3-b640-0daf50da5acb@oracle.com> Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) On Mon, Sep 23, 2024 at 12:57:32PM +1000, Dave Chinner wrote: > Ok, but that's not going to be widespread. Very little storage > hardware out there supports atomic writes - the vast majority of > deployments will be new hardware that will have mkfs run on it. Just about every enterprise NVMe SSD supports atomic write size larger than a single LBA, because it is completely natural fallout from FTL deѕign. That beeing said to support those SSDs a block size of 16 or 32k would be a lot more natural than all the forcealign madness.