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=-8.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham 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 D846CC433E0 for ; Tue, 9 Feb 2021 06:34:55 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 76F0964EB6 for ; Tue, 9 Feb 2021 06:34:55 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 76F0964EB6 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=nvidia.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 0C2316B0070; Tue, 9 Feb 2021 01:34:55 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 073616B0071; Tue, 9 Feb 2021 01:34:55 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id ECB958D0001; Tue, 9 Feb 2021 01:34:54 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0163.hostedemail.com [216.40.44.163]) by kanga.kvack.org (Postfix) with ESMTP id D84836B0070 for ; Tue, 9 Feb 2021 01:34:54 -0500 (EST) Received: from smtpin04.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id A140B18080D64 for ; Tue, 9 Feb 2021 06:34:54 +0000 (UTC) X-FDA: 77797766508.04.pets77_4f17fa127605 Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin04.hostedemail.com (Postfix) with ESMTP id 7D1E18026C6B for ; Tue, 9 Feb 2021 06:34:54 +0000 (UTC) X-HE-Tag: pets77_4f17fa127605 X-Filterd-Recvd-Size: 5164 Received: from hqnvemgate25.nvidia.com (hqnvemgate25.nvidia.com [216.228.121.64]) by imf19.hostedemail.com (Postfix) with ESMTP for ; Tue, 9 Feb 2021 06:34:53 +0000 (UTC) Received: from hqmail.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate25.nvidia.com (using TLS: TLSv1.2, AES256-SHA) id ; Mon, 08 Feb 2021 22:34:52 -0800 Received: from DRHQMAIL107.nvidia.com (10.27.9.16) by HQMAIL109.nvidia.com (172.20.187.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 9 Feb 2021 06:34:52 +0000 Received: from [10.2.50.67] (172.20.145.6) by DRHQMAIL107.nvidia.com (10.27.9.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 9 Feb 2021 06:34:51 +0000 Subject: Re: [PATCH v2] mm: cma: support sysfs From: John Hubbard To: Greg KH CC: Minchan Kim , Andrew Morton , linux-mm , LKML , , , References: <20210208180142.2765456-1-minchan@kernel.org> <43cd6fc4-5bc5-50ec-0252-ffe09afd68ea@nvidia.com> <7cc229f4-609c-71dd-9361-063ef1bf7c73@nvidia.com> Message-ID: Date: Mon, 8 Feb 2021 22:34:51 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:85.0) Gecko/20100101 Thunderbird/85.0 MIME-Version: 1.0 In-Reply-To: <7cc229f4-609c-71dd-9361-063ef1bf7c73@nvidia.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Originating-IP: [172.20.145.6] X-ClientProxiedBy: HQMAIL107.nvidia.com (172.20.187.13) To DRHQMAIL107.nvidia.com (10.27.9.16) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1612852492; bh=7wQ8mWS6cW2YEXFTB8AqiROB1gkp1bSnRoEhFMdaxfE=; h=Subject:From:To:CC:References:Message-ID:Date:User-Agent: MIME-Version:In-Reply-To:Content-Type:Content-Language: Content-Transfer-Encoding:X-Originating-IP:X-ClientProxiedBy; b=CNd1JzwwkAR7h5CPMTmCRnAErttwqaT/QE1c5UxltA6Oy/pJE8sTpRmUm/8AFaaAX ghxbUDJKrB17gSmhfDB8Jsx2wdjoXFaqmkRz1MgCAbo93ImML9YR4qVD2EtkCpcZYN +kQQvyY+X0GYCtoJVIfPHLvyjQjL23L+LWKcz9JOvlqNLaGLhB4peuKL9LQShtjaN5 a9ctGBlP7plDy+88/+glPGd751r6nqoCFo3rGDJ/+0C0KJ5ETPKCc7HdY2qqKxBbnd VMfCZbBU+lstKtevvWIJCCcTVfsBUTVyl0i5bwCUedkYdFjKK/zCSArb1QRvokRV9v Wofg+yQigrVMw== 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: On 2/8/21 10:27 PM, John Hubbard wrote: > On 2/8/21 10:13 PM, Greg KH wrote: >> On Mon, Feb 08, 2021 at 05:57:17PM -0800, John Hubbard wrote: >>> On 2/8/21 3:36 PM, Minchan Kim wrote: >>> ... >>>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 char name[CMA_MAX_NAME]; >>>>>> +#ifdef CONFIG_CMA_SYSFS >>>>>> +=C2=A0=C2=A0=C2=A0 struct cma_stat=C2=A0=C2=A0=C2=A0 *stat; >>>>> >>>>> This should not be a pointer. By making it a pointer, you've added a = bunch of pointless >>>>> extra code to the implementation. >>>> >>>> Originally, I went with the object lifetime with struct cma as you >>>> suggested to make code simple. However, Greg KH wanted to have >>>> release for kobj_type since it is consistent with other kboject >>>> handling. >>> >>> Are you talking about the kobj in your new struct cma_stat? That seems >>> like circular logic if so. I'm guessing Greg just wanted kobj methods >>> to be used *if* you are dealing with kobjects. That's a narrower point. >>> >>> I can't imagine that he would have insisted on having additional >>> allocations just so that kobj freeing methods could be used. :) >> >> Um, yes, I was :) >> >> You can not add a kobject to a structure and then somehow think you can >> just ignore the reference counting issues involved.=C2=A0 If a kobject i= s >> part of a structure then the kobject is responsible for controling the >> lifespan of the memory, nothing else can be. >> >> So by making the kobject dynamic, you properly handle that memory >> lifespan of the object, instead of having to worry about the lifespan of >> the larger object (which the original patch was not doing.) >> >> Does that make sense? >> > That part makes sense, yes, thanks. The part that I'm trying to straighte= n > out is, why was kobject even added to the struct cma_stat in the first > place? Why not just leave .stat as a static member variable, without > a kobject in it, and done? >=20 Sorry, I think I get it now: this is in order to allow a separate lifetime for the .stat member. I was sort of implicitly assuming that the "right" way to do it is just have the whole object use one lifetime management, but as you say, there is no kobject being added to the parent. I still feel odd about the allocation and freeing of something that seems to be logically the same lifetime (other than perhaps a few, briefly pendin= g sysfs reads, at the end of life). So I'd still think that the kobject shoul= d be added to the parent... thanks, --=20 John Hubbard NVIDIA