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 X-Spam-Level: X-Spam-Status: No, score=-2.0 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8AED4CA9EA0 for ; Fri, 25 Oct 2019 08:31:14 +0000 (UTC) Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id EA54321929; Fri, 25 Oct 2019 08:31:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=sourceforge.net header.i=@sourceforge.net header.b="V26llUaW"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=sf.net header.i=@sf.net header.b="HnoUM9rh" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EA54321929 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linux-f2fs-devel-bounces@lists.sourceforge.net Received: from [127.0.0.1] (helo=sfs-ml-1.v29.lw.sourceforge.com) by sfs-ml-1.v29.lw.sourceforge.com with esmtp (Exim 4.90_1) (envelope-from ) id 1iNv05-0003w9-I7; Fri, 25 Oct 2019 08:31:13 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-1.v29.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1iNv04-0003vn-Ao for linux-f2fs-devel@lists.sourceforge.net; Fri, 25 Oct 2019 08:31:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:CC:To:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Dq7r46Qy3h5/A2nRc4eIYBiM22Riuv04KRUAOCbzY+M=; b=V26llUaWlbMowEdU9UVwSjxeiy QHn/ZJhvsCEIeh4igIxs73FwWZ4+SKIgLfNAopW/WNFu/FK+22prvSJ0ZG4/c4wzWrmjdNvSPMCPX FUkeH5D6GH05xPfjndIcfkgfnmqQ4eKKWEUO0THaS7mMoEZdPCSyeJeerIPkZXqy4txU=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:References:CC:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=Dq7r46Qy3h5/A2nRc4eIYBiM22Riuv04KRUAOCbzY+M=; b=HnoUM9rhVbm4KQzS77W3IV4rNo UDZJmFKIbqEYM9gnd2xNGO0K26W32vQuzjqUeE+DF0Dfi+XFzSVIP8groFTZ35Hyn2d1p+824CqI8 1sGL2qU4Tn9oJm50HXtr98gkzB3sBb9JP+yh1JckDuslROehZu7I+JhsaIuZRlphJCb4=; Received: from szxga04-in.huawei.com ([45.249.212.190] helo=huawei.com) by sfi-mx-3.v28.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.2) id 1iNv00-0036mI-LO for linux-f2fs-devel@lists.sourceforge.net; Fri, 25 Oct 2019 08:31:12 +0000 Received: from DGGEMS412-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 4A36215660F7E19A1B36; Fri, 25 Oct 2019 16:31:01 +0800 (CST) Received: from [10.134.22.195] (10.134.22.195) by smtp.huawei.com (10.3.19.212) with Microsoft SMTP Server (TLS) id 14.3.439.0; Fri, 25 Oct 2019 16:30:56 +0800 To: Hridya Valsaraju References: <20191023214821.107615-1-hridya@google.com> <20191023214821.107615-2-hridya@google.com> From: Chao Yu Message-ID: <96f89e7c-d91e-e263-99f7-16998cc443a7@huawei.com> Date: Fri, 25 Oct 2019 16:30:57 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-Originating-IP: [10.134.22.195] X-CFilter-Loop: Reflected X-Headers-End: 1iNv00-0036mI-LO Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: Add f2fs stats to sysfs X-BeenThere: linux-f2fs-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Jaegeuk Kim , Android Kernel Team , LKML , linux-f2fs-devel@lists.sourceforge.net Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net On 2019/10/25 11:51, Hridya Valsaraju wrote: > On Thu, Oct 24, 2019 at 2:26 AM Chao Yu wrote: >> >> On 2019/10/24 5:48, Hridya Valsaraju wrote: >>> Currently f2fs stats are only available from /d/f2fs/status. This patch >>> adds some of the f2fs stats to sysfs so that they are accessible even >>> when debugfs is not mounted. >> >> Why don't we mount debugfs first? > > Thank you for taking a look at the patch Chao. We will not be mounting > debugfs for security reasons. Hi, Hridya, May I ask is there any use case for those new entries? So many sysfs entries exist, if there is real use case, how about backuping entire /d/f2fs/status entry into /proc/fs/f2fs// directory rather than adding some of stats as a single entry in sysfs directory? Thanks, > > Regards, > Hridya > >> >> Thanks, > . > _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel