Received: by 2002:a05:7412:b101:b0:e2:908c:2ebd with SMTP id az1csp2673537rdb; Wed, 15 Nov 2023 07:31:46 -0800 (PST) X-Google-Smtp-Source: AGHT+IHiwIufgEhFICkWgaSoNNmQpz9A1TPfHehohTXJPG4uuYflODHLFDUwMXyHtHObH4Lol0UA X-Received: by 2002:a17:902:efc7:b0:1cc:7ebe:4db6 with SMTP id ja7-20020a170902efc700b001cc7ebe4db6mr5906987plb.39.1700062305598; Wed, 15 Nov 2023 07:31:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1700062305; cv=none; d=google.com; s=arc-20160816; b=dqNmG+nKGDgEyTXlmlf+VQwRBvVnxcHJ/GYsEK/1Fw5kgQ/AWZ4ARsl7UaBnl5gsQj Ef89dKgvWOClr4Y5DKfe8Q21ZAZ8lU3vgZ9j2/PxCojwG0cKPENRi/dfTYDf1snOUccy 9EP/Y35C3sCsfFz7380XJCQ2L+OHSNJ1dHw1aSTMu8C30NXfvtuO6Z0EHktqOFBeVTpu dRC8el8dPHJbRWCBFIly9n3fbB1I8cFRHqYDQKgCNyi5bDHdIVAF+QMtr9yoa5Ex71il qsMgQ1L4+lBadmIMKSccdQ1PxpB/W5Ljp4Loazq+quITIIF3noYbRlJnvLeuk4U5k1aj 0HRg== 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=x0ww2NaDEpoBqF699F0PH7f66Q17NF2vZrmc+hjJMMk=; fh=oS2JRRUtvIxFucmgjdUMwLvcyv1fCt/Wd43w+FH9E0Q=; b=rUklI2sOFA/G05Wd744jVCe9lJb8H/Us5dbbsEHwmDr5zT5kdGeQzh+D3RoLJnWt7B 33vLrWzTptLqlAAt7E/x7NHcNEjo9yEOB0I2UpLEvU0YPJPCUkis1JnjLzOUWtOmZF/R gBHyxVyxyDtAlvkeagYMrZOUqa5VND5E3aZT8PVpRwEG8qkkQkHj2ZMRVmH+I366NYj0 f9r1UsWDjas2uPf9cRZywE0XeWqIeUtTNBdZxRHxIWDABGKqMXxY5S8Pmt+6QiT3kmKY DjJ1eWXaI/oqv6J2RuAoXOnYY4q5mbClhlHv36f3xaBgrUXeu9S04Z1SZiqgLtcrXPbt b0OQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=HLdrNUuj; 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 b20-20020a631b54000000b005a0018ec786si9907092pgm.854.2023.11.15.07.31.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 Nov 2023 07:31:45 -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=HLdrNUuj; 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 5AA388023A19; Wed, 15 Nov 2023 07:31:25 -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 S229886AbjKOPbC (ORCPT + 99 others); Wed, 15 Nov 2023 10:31:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59828 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229511AbjKOPbB (ORCPT ); Wed, 15 Nov 2023 10:31:01 -0500 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 003DE1A1; Wed, 15 Nov 2023 07:30:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1700062259; x=1731598259; h=date:from:to:cc:subject:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=x0ww2NaDEpoBqF699F0PH7f66Q17NF2vZrmc+hjJMMk=; b=HLdrNUujWcyMUNPxabFFliD/tpY6gMiii/tAaJJQ+ETc2WPdB2GhVkBZ AB+OY84r2ZU2pMb3O0nhQ0FciUtCbwatU7kLG0PXLMBRoann0Ha2tIz63 bHtqykr4uqLmqGh/HEm5GqQdROfA7P0ayKY6DuUnYI1SQ681CujIgpRrw +06iS60jRO0W3U92Z47eIAYrB2Il6hj+panyemqk5SjhMSIxASAKn3o9k 0+cUvW+kJmEAY/MQEeX+QaxBBIhynDq7kqEcNwtX/oG/rQeHy9a0GbO1y /3u0xP8Icjw44x9UwevjuRf0L9vcSzrfjLV+qX5Csyb/nvJa+vYTVxGu8 g==; X-IronPort-AV: E=McAfee;i="6600,9927,10895"; a="370241814" X-IronPort-AV: E=Sophos;i="6.03,305,1694761200"; d="scan'208";a="370241814" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Nov 2023 07:30:58 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10895"; a="1096477268" X-IronPort-AV: E=Sophos;i="6.03,305,1694761200"; d="scan'208";a="1096477268" Received: from mtkaczyk-mobl.ger.corp.intel.com (HELO localhost) ([10.249.135.68]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Nov 2023 07:30:56 -0800 Date: Wed, 15 Nov 2023 16:30:51 +0100 From: Mariusz Tkaczyk To: junxiao.bi@oracle.com, Song Liu Cc: 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: <20231115162915.000064f8@linux.intel.com> In-Reply-To: <443775e1-ed94-452e-8f06-eadb777bede4@oracle.com> References: <20231114185947.42829-1-junxiao.bi@oracle.com> <443775e1-ed94-452e-8f06-eadb777bede4@oracle.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: quoted-printable X-Spam-Status: No, score=-0.9 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 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]); Wed, 15 Nov 2023 07:31:25 -0800 (PST) On Tue, 14 Nov 2023 15:53:47 -0800 junxiao.bi@oracle.com wrote: > Understood, thanks. Sound like depending on Userspace on memory reclaim=20 > path is really bad idea and the only option for fixing it is to remove=20 > that dependency, but i am not sure that is possible without breaking the= =20 > consistency of metadata. >=20 > Thanks, >=20 > Junxiao. Indeed the project of external metadata management if fragile. You cares ab= out 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 meta= data management in kernel. Song, any comments here? =46rom the second hand, there is native raid which should just work, so maybe= you can switch to the native raid? Thanks, Mariusz