On Wed, Jul 2, 2025 at 5:46 PM Vishal Annapurve <vannapurve@xxxxxxxxxx> wrote: > ... > > > > 2) There are some use-cases for HugeTLB + CoCo that have come to my > > attention recently that put a lot of weight on still being able to > > maximize mapping/hugepage size when accessing shared mem from userspace, > > e.g. for certain DPDK workloads that accessed shared guest buffers > > from host userspace. We don't really have a story for this, and I > > wouldn't expect us to at this stage, but I think it ties into #1 so > > might be worth considering in that context. > > Major problem I see here is that if anything in the kernel does a GUP > on shared memory ranges (which is very likely to happen), it would be > difficult to get them to let go of the whole hugepage before it can be > split safely. The scenario I was alluding to here: guest trying to convert a subpage from a shared range backed by hugepage to private.
