[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241031181242.96312cd4eff58ba2369342c8@linux-foundation.org>
Date: Thu, 31 Oct 2024 18:12:42 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Maíra Canal <mcanal@...lia.com>
Cc: Jonathan Corbet <corbet@....net>, Hugh Dickins <hughd@...gle.com>, Barry
Song <baohua@...nel.org>, David Hildenbrand <david@...hat.com>, Ryan
Roberts <ryan.roberts@....com>, Baolin Wang
<baolin.wang@...ux.alibaba.com>, Lance Yang <ioworker0@...il.com>,
linux-mm@...ck.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel-dev@...lia.com
Subject: Re: [PATCH v3 0/4] mm: add more kernel parameters to control mTHP
On Thu, 31 Oct 2024 08:04:58 -0300 Maíra Canal <mcanal@...lia.com> wrote:
> > There isn't a lot of info here - please explain this timing issue in
> > more detail.
> >
> > Because the question which leaps to mind is: shouldn't the
> > "applications that use shmem" be changed to "configure mTHP through
> > sysfs" *before* "using shmem"? Seems pretty basic.
>
> Sorry about that, I'll try to improve the commit messages and add more
> details.
>
> As mentioned in the example I gave ("DRM GEM objects"), my main use is
> GEM objects backed by shmem. I'd like to use Huge Pages on the GPU and I
> can only do that if I have contiguous memory to back my objects.
>
> I can't think how I can change sysfs from a DRM driver.
So your term "applications" actually refers to in-kernel drivers?
Powered by blists - more mailing lists