From: John Hubbard <jhubbard@nvidia.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>, <surenb@google.com>,
<joaodias@google.com>, <willy@infradead.org>
Subject: Re: [PATCH v2] mm: cma: support sysfs
Date: Tue, 9 Feb 2021 23:50:43 -0800 [thread overview]
Message-ID: <2abc0258-d71a-56f2-3682-cc178f3ce4c4@nvidia.com> (raw)
In-Reply-To: <YCOKpM9lufhD/myy@kroah.com>
On 2/9/21 11:26 PM, Greg KH wrote:
...
>> I just am not especially happy about the inability to do natural, efficient
>> things here, such as use a statically allocated set of things with sysfs. And
>> I remain convinced that the above is not "improper"; it's a reasonable
>> step, given the limitations of the current sysfs design. I just wanted to say
>> that out loud, as my proposal sinks to the bottom of the trench here. haha :)
>
> What is "odd" is that you are creating an object in the kernel that you
> _never_ free. That's not normal at all in the kernel, and so, your wish
> to have a kobject that you never free represent this object also is not
> normal :)
>
OK, thanks for taking the time to explain that, much appreciated!
thanks,
--
John Hubbard
NVIDIA
prev parent reply other threads:[~2021-02-10 7:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 18:01 Minchan Kim
2021-02-08 21:34 ` John Hubbard
2021-02-08 23:36 ` Minchan Kim
2021-02-09 1:57 ` John Hubbard
2021-02-09 4:19 ` Minchan Kim
2021-02-09 5:18 ` John Hubbard
2021-02-09 5:27 ` John Hubbard
2021-02-09 6:13 ` Greg KH
2021-02-09 6:27 ` John Hubbard
2021-02-09 6:34 ` John Hubbard
2021-02-09 6:56 ` Greg KH
2021-02-09 15:55 ` Minchan Kim
2021-02-09 17:49 ` Greg KH
2021-02-09 20:11 ` John Hubbard
2021-02-09 21:13 ` Minchan Kim
2021-02-10 6:43 ` Greg KH
2021-02-10 7:12 ` Minchan Kim
2021-02-10 7:16 ` John Hubbard
2021-02-10 7:26 ` Greg KH
2021-02-10 7:50 ` John Hubbard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2abc0258-d71a-56f2-3682-cc178f3ce4c4@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=joaodias@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=surenb@google.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox