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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9452DC433EF for ; Thu, 21 Apr 2022 01:20:51 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id EFABA6B0071; Wed, 20 Apr 2022 21:20:50 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id EAC066B0073; Wed, 20 Apr 2022 21:20:50 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D73146B0074; Wed, 20 Apr 2022 21:20:50 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.27]) by kanga.kvack.org (Postfix) with ESMTP id C82306B0071 for ; Wed, 20 Apr 2022 21:20:50 -0400 (EDT) Received: from smtpin07.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id 93E356057E for ; Thu, 21 Apr 2022 01:20:50 +0000 (UTC) X-FDA: 79379131860.07.B63C327 Received: from mail104.syd.optusnet.com.au (mail104.syd.optusnet.com.au [211.29.132.246]) by imf11.hostedemail.com (Postfix) with ESMTP id DF5424001D for ; Thu, 21 Apr 2022 01:20:47 +0000 (UTC) Received: from dread.disaster.area (pa49-181-115-138.pa.nsw.optusnet.com.au [49.181.115.138]) by mail104.syd.optusnet.com.au (Postfix) with ESMTPS id A59B8534640; Thu, 21 Apr 2022 11:20:46 +1000 (AEST) Received: from dave by dread.disaster.area with local (Exim 4.92.3) (envelope-from ) id 1nhLUz-002b2q-G6; Thu, 21 Apr 2022 11:20:45 +1000 Date: Thu, 21 Apr 2022 11:20:45 +1000 From: Dave Chinner To: Shiyang Ruan Cc: linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org, nvdimm@lists.linux.dev, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, djwong@kernel.org, dan.j.williams@intel.com, hch@infradead.org, jane.chu@oracle.com Subject: Re: [PATCH v13 0/7] fsdax: introduce fs query to support reflink Message-ID: <20220421012045.GR1544202@dread.disaster.area> References: <20220419045045.1664996-1-ruansy.fnst@fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220419045045.1664996-1-ruansy.fnst@fujitsu.com> X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.4 cv=deDjYVbe c=1 sm=1 tr=0 ts=6260b170 a=/kVtbFzwtM2bJgxRVb+eeA==:117 a=/kVtbFzwtM2bJgxRVb+eeA==:17 a=kj9zAlcOel0A:10 a=z0gMJWrwH1QA:10 a=7-415B0cAAAA:8 a=7EZY2-qYyHQqCbfsKPUA:9 a=CjuIK1q_8ugA:10 a=biEYGPWJfzWAr4FL6Ov7:22 X-Rspam-User: X-Rspamd-Server: rspam11 X-Rspamd-Queue-Id: DF5424001D X-Stat-Signature: 18xepaqwderc8mbu4iexbc9sgm7okt97 Authentication-Results: imf11.hostedemail.com; dkim=none; dmarc=none; spf=none (imf11.hostedemail.com: domain of david@fromorbit.com has no SPF policy when checking 211.29.132.246) smtp.mailfrom=david@fromorbit.com X-HE-Tag: 1650504047-241206 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Hi Ruan, On Tue, Apr 19, 2022 at 12:50:38PM +0800, Shiyang Ruan wrote: > This patchset is aimed to support shared pages tracking for fsdax. Now that this is largely reviewed, it's time to work out the logistics of merging it. > Changes since V12: > - Rebased onto next-20220414 What does this depend on that is in the linux-next kernel? i.e. can this be applied successfully to a v5.18-rc2 kernel without needing to drag in any other patchsets/commits/trees? What are your plans for the followup patches that enable reflink+fsdax in XFS? AFAICT that patchset hasn't been posted for while so I don't know what it's status is. Is that patchset anywhere near ready for merge in this cycle? If that patchset is not a candidate for this cycle, then it largely doesn't matter what tree this is merged through as there shouldn't be any major XFS or dax dependencies being built on top of it during this cycle. The filesystem side changes are isolated and won't conflict with other work in XFS, either, so this could easily go through Dan's tree. However, if the reflink enablement is ready to go, then this all needs to be in the XFS tree so that we can run it through filesystem level DAX+reflink testing. That will mean we need this in a stable shared topic branch and tighter co-ordination between the trees. So before we go any further we need to know if the dax+reflink enablement patchset is near being ready to merge.... Cheers, Dave. -- Dave Chinner david@fromorbit.com