From: Boris Brezillon <boris.brezillon@collabora.com>
To: "Loïc Molinari" <loic.molinari@collabora.com>
Cc: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Rob Herring" <robh@kernel.org>,
"Steven Price" <steven.price@arm.com>,
"Liviu Dudau" <liviu.dudau@arm.com>,
"Melissa Wen" <mwen@igalia.com>,
"Maíra Canal" <mcanal@igalia.com>,
"Hugh Dickins" <hughd@google.com>,
"Baolin Wang" <baolin.wang@linux.alibaba.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Mikołaj Wasiak" <mikolaj.wasiak@intel.com>,
"Christian Brauner" <brauner@kernel.org>,
"Nitin Gote" <nitin.r.gote@intel.com>,
"Andi Shyti" <andi.shyti@linux.intel.com>,
"Christopher Healy" <healych@amazon.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, linux-mm@kvack.org,
kernel@collabora.com
Subject: Re: [PATCH v3 05/10] drm/v3d: Use huge tmpfs mount point helper
Date: Mon, 6 Oct 2025 09:07:30 +0200 [thread overview]
Message-ID: <20251006090730.364a1713@fedora> (raw)
In-Reply-To: <20251004093054.21388-6-loic.molinari@collabora.com>
On Sat, 4 Oct 2025 11:30:48 +0200
Loïc Molinari <loic.molinari@collabora.com> wrote:
> +static void
> +v3d_huge_mnt_init(struct v3d_dev *v3d)
> +{
> + int err;
> +
> + /*
> + * By creating our own shmemfs mountpoint, we can pass in
> + * mount flags that better match our usecase. However, we
> + * only do so on platforms which benefit from it.
> + */
> + if (!IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE))
> + goto err;
> +
> + /* The user doesn't want to enable Super Pages */
> + if (!super_pages)
> + goto err;
> +
> + err = drm_gem_huge_mnt_create(&v3d->drm, "within_size");
> + if (err && err != -EEXIST)
> + goto err;
> +
> + drm_info(&v3d->drm, "Using Transparent Hugepages\n");
> +
> + return;
> +
> +err:
> + drm_notice(&v3d->drm,
> + "Transparent Hugepage support is recommended for optimal performance on this platform!\n");
With the changes suggested on patch 3, this can be shrunk a little bit:
int err = 0;
if (super_pages)
err = drm_gem_huge_mnt_create(&v3d->drm, "within_size");
if (v3d->drm.huge_mnt)
drm_info(&v3d->drm, "Using Transparent Hugepages\n");
else if (!err)
drm_notice(&v3d->drm,
"Transparent Hugepage support is recommended for optimal performance on this platform!\n");
else
drm_warn(&v3d->drm, "Couldn't create THP mount point (err=%d)\n", err);
next prev parent reply other threads:[~2025-10-06 7:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-04 9:30 [PATCH v3 00/10] drm: Reduce page tables overhead with THP Loïc Molinari
2025-10-04 9:30 ` [PATCH v3 01/10] drm/shmem-helper: Add huge page fault handler Loïc Molinari
2025-10-04 22:53 ` Matthew Wilcox
2025-10-06 6:52 ` Boris Brezillon
2025-10-06 16:01 ` Andi Shyti
2025-10-04 9:30 ` [PATCH v3 02/10] drm/gem: Introduce drm_gem_get_unmapped_area() fop Loïc Molinari
2025-10-10 7:48 ` kernel test robot
2025-10-04 9:30 ` [PATCH v3 03/10] drm/gem: Add huge tmpfs mount point helper Loïc Molinari
2025-10-04 20:34 ` Al Viro
2025-10-06 6:58 ` Boris Brezillon
2025-10-06 7:02 ` Boris Brezillon
2025-10-04 9:30 ` [PATCH v3 04/10] drm/i915: Use " Loïc Molinari
2025-10-04 9:30 ` [PATCH v3 05/10] drm/v3d: " Loïc Molinari
2025-10-06 7:07 ` Boris Brezillon [this message]
2025-10-04 9:30 ` [PATCH v3 06/10] drm/gem: Get rid of *_with_mnt helpers Loïc Molinari
2025-10-06 7:17 ` Boris Brezillon
2025-10-04 9:30 ` [PATCH v3 07/10] drm/panthor: Introduce huge tmpfs mount point option Loïc Molinari
2025-10-06 7:28 ` Boris Brezillon
2025-10-15 13:09 ` Loïc Molinari
2025-10-15 13:12 ` Boris Brezillon
2025-10-06 7:34 ` Boris Brezillon
2025-10-04 9:30 ` [PATCH v3 08/10] drm/panthor: Improve IOMMU map/unmap debugging logs Loïc Molinari
2025-10-04 9:30 ` [PATCH v3 09/10] drm/panfrost: Introduce huge tmpfs mount point option Loïc Molinari
2025-10-06 7:33 ` Boris Brezillon
2025-10-04 9:30 ` [PATCH v3 10/10] Documentation/gpu/drm-mm: Add THP paragraph to GEM mapping section Loïc Molinari
2025-10-04 22:40 ` Bagas Sanjaya
2025-10-04 10:42 ` ✓ i915.CI.BAT: success for series starting with [v3,01/10] drm/shmem-helper: Add huge page fault handler Patchwork
2025-10-04 12:26 ` ✗ i915.CI.Full: failure " Patchwork
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=20251006090730.364a1713@fedora \
--to=boris.brezillon@collabora.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andi.shyti@linux.intel.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=brauner@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=healych@amazon.com \
--cc=hughd@google.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liviu.dudau@arm.com \
--cc=loic.molinari@collabora.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcanal@igalia.com \
--cc=mikolaj.wasiak@intel.com \
--cc=mripard@kernel.org \
--cc=mwen@igalia.com \
--cc=nitin.r.gote@intel.com \
--cc=robh@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.