The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Saravanan D <saravanand@crusoe.ai>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org,  David Hildenbrand <david@kernel.org>,
	Zi Yan <ziy@nvidia.com>,
	 Baolin Wang <baolin.wang@linux.alibaba.com>,
	"Liam R . Howlett" <liam@infradead.org>,
	 Nico Pache <nico.pache@linux.dev>,
	Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
	 Barry Song <baohua@kernel.org>,
	Lance Yang <lance.yang@linux.dev>,
	 Usama Arif <usama.arif@linux.dev>, Peter Xu <peterx@redhat.com>,
	 Alex Williamson <alex.williamson@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/huge_memory: allow huge pfnmaps regardless of THP mode
Date: Sat, 22 Aug 2026 15:29:46 +0100	[thread overview]
Message-ID: <aomyM47kVsW_v-Cm@gremlin> (raw)
In-Reply-To: <20260821193220.91799-1-saravanand@crusoe.ai>

On Fri, Aug 21, 2026 at 12:32:20PM -0700, Saravanan D wrote:
> On Fri, Aug 21, 2026 at 09:03:15AM +0100, Lorenzo Stoakes (ARM) wrote:
> > In any case if you'd taken 5 minutes to search the mailing list you'd see
> > this was:
> >
> > a. Already submitted (so your patch reads like plagiarism).
> > b. Already rejected in favour of me doing an actually sensible solution.
> >
> > https://lore.kernel.org/linux-mm/anL-NZkNMSSxN0YN@lucifer/
>
> Apologies and please disregard my patch. I had not
> searched the list before sending and was unaware of Cédric's patch
> and your rework. Mine came from an independent observation of slow
> VM boot times on Ubuntu based hosts running cloud-hypervisor with H100
> GPUs. The patch was prepared with AI assistance and should have
> carried an Assisted-by tag. All of my future submissions will.
>
> I backported the diff you attached in your earlier response to
> a 6.17 based kernel and ran it on a HGX host with four H100 GPUs,
> each exposing a 128 GiB BAR1, with cloud-hypervisor. THP
> mode was the Ubuntu default - madvise in all runs.
>
>                        VFIO_IOMMU_MAP_DMA       4 GPU VM boot
>                        per 128 GiB BAR
>   6.17 unpatched             20.7s                   97s
>   6.17 + your diff            0.4s                   17s
>
> Each BAR mapped with 128 PUD faults. Your approach will definitely
> improve VM boot times in our production. Very grateful for your
> contribution.

Thanks, always appreciate real world data :)

I will send the actual patch at some point it's on my never ending TODO
list... :)

>
> Thanks,
> Saravanan D.

--
Cheers, Lorenzo

      reply	other threads:[~2026-08-22 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21  7:05 [PATCH] mm/huge_memory: allow huge pfnmaps regardless of THP mode Saravanan D
2026-08-21  8:03 ` Lorenzo Stoakes (ARM)
2026-08-21 19:32   ` Saravanan D
2026-08-22 14:29     ` Lorenzo Stoakes (ARM) [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=aomyM47kVsW_v-Cm@gremlin \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alex.williamson@redhat.com \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=lance.yang@linux.dev \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nico.pache@linux.dev \
    --cc=peterx@redhat.com \
    --cc=ryan.roberts@arm.com \
    --cc=saravanand@crusoe.ai \
    --cc=usama.arif@linux.dev \
    --cc=ziy@nvidia.com \
    /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