Received: by 2002:a05:7412:b130:b0:e2:908c:2ebd with SMTP id az48csp366301rdb; Fri, 17 Nov 2023 00:37:06 -0800 (PST) X-Google-Smtp-Source: AGHT+IGu46yXKwQ0z1yh0FgrCeTkOpBroq/j3rzHkMyL3ROhqvYR8ohT31jkRQonrt0s4vP88vTC X-Received: by 2002:a17:90b:1a8a:b0:280:ca28:de58 with SMTP id ng10-20020a17090b1a8a00b00280ca28de58mr6505735pjb.4.1700210226104; Fri, 17 Nov 2023 00:37:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1700210226; cv=none; d=google.com; s=arc-20160816; b=tmXZknv4QxNaqJ7tcwAIZlsviC4fGaNFiqffOHMV3q6Ea6q7RmtitVSMLpBZhlTg4j rAAPB4KicgAumqvSrqxgGf+OVe4qFLp2jVJYa9FvBb7VtjgRjJ2rimvRYL+fOMrrPqCk riRKRX3mJshL1VuAau2Zm2R+Fp1pg+1SeOjDZVIrDDGnHBh0zIJjjnYFNfnt7SP8hXiv S/mihPqvuznBpvYHsx5AGFnfGYG8jX+90jpjfkc8cnLAZ9wtcqVjB8NY0rB3vxQJwaTp DG498eQGVKAYjx3P0bEnyLKMTYs3oc+hWHETUHAxoJTF8f53b/cEptX5INEZDKI8Ow1f mMUg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=lfpFqTSS6e82KEVKmFjVgHr8oJr7lFwDYnHxWgeW3JQ=; fh=J+Vy7o+JsrB+ESucQ9t5Mj06BQQoAb6ODKAvxGzhaus=; b=EMlJddofWgH4RL7vHbDuTYK88kmKCf0XCgRbxmZr7Vxr+vaqQuyjXT1uHR9/lixtiG Vck2NqhvpOE3iDwlrBEOGDr3T8E060Da1o5s4o2DNSxeBfC2aWds8TfQ/etzg9+ytWCh onMwN69heOGNFkjGF4Q+jI7eSYG3uG6aiB6cZbDXreiSsA8ikvEK7RMxUxO3hzx7+x5q S8Da/gEdxrU/iiiYPCJUl4wcjo/3tphK1t80NCN8Fo0zT5NxI2ISF3XCS8HB83NlyGKz Z71iWkVwDRBRfnPVAMAZHrhsy661piXFJ+JXgcrIzIeoxnwSHVbGzHC5Fv1rpWWJYior e1Pg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=KszBwRCP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from agentk.vger.email (agentk.vger.email. [2620:137:e000::3:2]) by mx.google.com with ESMTPS id v22-20020a17090ae99600b002839d007771si365582pjy.55.2023.11.17.00.37.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 17 Nov 2023 00:37:06 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) client-ip=2620:137:e000::3:2; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=KszBwRCP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by agentk.vger.email (Postfix) with ESMTP id 5E08781C00DA; Fri, 17 Nov 2023 00:37:03 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at agentk.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230376AbjKQIgx (ORCPT + 99 others); Fri, 17 Nov 2023 03:36:53 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58736 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229599AbjKQIgw (ORCPT ); Fri, 17 Nov 2023 03:36:52 -0500 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.9]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 51BBFB0; Fri, 17 Nov 2023 00:36:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1700210209; x=1731746209; h=date:from:to:cc:subject:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=sPWTdnpNJUc5dfTVsK5EG0pPjOoquKeW81JBrUka9FU=; b=KszBwRCPxDfZpAYOgB5Veh/w/NHuy7gT+EFX+Hy3cvNXdIw0RgeBAEbW Qhezz7BHud4Hzr8D0kOreGnYdVNH/aR5SohGZuDvWGYNaQG9Q2jpBcNit DKOpDpjIpmCIAMLiiI7jT22A7oKGZisW9sSqMo2FFLhvw5EX1b4NShG0/ xigbUqtXmkn4jKpsMl9j8UClYKPIVCEXF/La7dttmhyuZdrugpHzs9HrK 0Y7pPZZl6L/B9ew1XP38tPSFfqgft6gq5Ou4qoiSP264VWfY15K39i2pv QFrnozt2HAcba8f1KDogvQu1guGL0tC1DIIjVkNoRTEhZBBzeVhgDk5ZN g==; X-IronPort-AV: E=McAfee;i="6600,9927,10896"; a="9920714" X-IronPort-AV: E=Sophos;i="6.04,206,1695711600"; d="scan'208";a="9920714" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orvoesa101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Nov 2023 00:36:48 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10896"; a="769165246" X-IronPort-AV: E=Sophos;i="6.04,206,1695711600"; d="scan'208";a="769165246" Received: from kkrolx-mobl2.ger.corp.intel.com (HELO localhost) ([10.249.134.254]) by fmsmga007-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Nov 2023 00:36:46 -0800 Date: Fri, 17 Nov 2023 09:36:40 +0100 From: Mariusz Tkaczyk To: junxiao.bi@oracle.com Cc: Song Liu , Tejun Heo , linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org, gregkh@linuxfoundation.org Subject: Re: [PATCH] kernfs: support kernfs notify in memory recliam context Message-ID: <20231117093640.00006b70@linux.intel.com> In-Reply-To: References: <20231114185947.42829-1-junxiao.bi@oracle.com> <443775e1-ed94-452e-8f06-eadb777bede4@oracle.com> <20231115162915.000064f8@linux.intel.com> X-Mailer: Claws Mail 4.1.0 (GTK 3.24.33; x86_64-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on agentk.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (agentk.vger.email [0.0.0.0]); Fri, 17 Nov 2023 00:37:03 -0800 (PST) On Thu, 16 Nov 2023 09:04:34 -0800 junxiao.bi@oracle.com wrote: > On 11/15/23 7:30 AM, Mariusz Tkaczyk wrote: > > > On Tue, 14 Nov 2023 15:53:47 -0800 > > junxiao.bi@oracle.com wrote: > > > >> Understood, thanks. Sound like depending on Userspace on memory reclaim > >> path is really bad idea and the only option for fixing it is to remove > >> that dependency, but i am not sure that is possible without breaking the > >> consistency of metadata. > >> > >> Thanks, > >> > >> Junxiao. > > Indeed the project of external metadata management if fragile. You cares > > about IMSM here (same as me) so ideally we should implement metadata > > management in kernel- I think that IMSM deserved that after 10 years on the > > market. There is no better option, other options are just "workarounds" for > > the lack of metadata management in kernel. > Agree, sound like that's the way to proceed. > > > > Song, any comments here? > > > > From the second hand, there is native raid which should just work, so > > maybe you can switch to the native raid? > > Unfortunately that's is not possible, it's a production setup to use > imsm raid. Implementing IMSM in kernel is a goal for months/ years so I don't see it in a timeline you would need that on to fix your production setup. It will be a big feature, but let's wait for Song voice first. Thanks, Mariusz