On 3/1/20 5:04 AM, Andrew Morton wrote:
On Fri, 28 Feb 2020 14:08:04 +0100 Thomas Hellström (VMware)
wrote:
I'm wondering what's the best way here to get the patches touching mm
reviewed and accepted?
While drm people and VMware internal people have looked at them, I think
the huge_fault() fa
On Fri 28-02-20 14:08:04, Thomas Hellström (VMware) wrote:
> Andrew, Michal
>
> I'm wondering what's the best way here to get the patches touching mm
> reviewed and accepted?
I am sorry, but I am busy with other stuff and unlikely to find time to
review this series.
--
Michal Hocko
SUSE Labs
___
On Fri, 28 Feb 2020 14:08:04 +0100 Thomas Hellström (VMware)
wrote:
> I'm wondering what's the best way here to get the patches touching mm
> reviewed and accepted?
> While drm people and VMware internal people have looked at them, I think
> the huge_fault() fallback splitting and the introduc
Andrew, Michal
I'm wondering what's the best way here to get the patches touching mm
reviewed and accepted?
While drm people and VMware internal people have looked at them, I think
the huge_fault() fallback splitting and the introduction of
vma_is_special_huge() needs looking at more thoroughl
In order to reduce TLB misses and CPU usage this patchset enables huge-
and giant page-table entries for TTM and TTM-enabled graphics drivers.
Patch 1 and 2 introduce a vma_is_special_huge() function to make the mm code
take the same path as DAX when splitting huge- and giant page table entries,
(
