[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0100016a6e7a22d8-dcd24705-508f-4acc-8883-e5d61f4c0fa4-000000@email.amazonses.com>
Date: Tue, 30 Apr 2019 13:40:59 +0000
From: Christopher Lameter <cl@...ux.com>
To: Christoph Hellwig <hch@...radead.org>
cc: "Luck, Tony" <tony.luck@...el.com>, Meelis Roos <mroos@...ux.ee>,
Mel Gorman <mgorman@...hsingularity.net>,
Andrew Morton <akpm@...ux-foundation.org>,
Mikulas Patocka <mpatocka@...hat.com>,
James Bottomley <James.Bottomley@...senpartnership.com>,
"linux-parisc@...r.kernel.org" <linux-parisc@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Vlastimil Babka <vbabka@...e.cz>,
LKML <linux-kernel@...r.kernel.org>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>
Subject: Re: DISCONTIGMEM is deprecated
On Mon, 29 Apr 2019, Christoph Hellwig wrote:
> So maybe it it time to mark SN2 broken and see if anyone screams?
>
> Without SN2 the whole machvec mess could basically go away - the
> only real difference between the remaining machvecs is which iommu
> if any we set up.
SPARSEMEM with VMEMMAP was developed to address these
issues and allow one mapping scheme across the different platforms.
You do not need DISCONTIGMEM support for SN2. And as far as I know (from a
decade ago ok....) the distributions were using VMEMMAP instead.
Powered by blists - more mailing lists