[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <83cfd2d7-b840-b0c6-594e-8b39be8177c1@deltatee.com>
Date: Thu, 11 Oct 2018 12:45:56 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Christoph Hellwig <hch@....de>
Cc: Rob Herring <robh@...nel.org>, Albert Ou <aou@...s.berkeley.edu>,
Andrew Waterman <andrew@...ive.com>, linux-sh@...r.kernel.org,
Palmer Dabbelt <palmer@...ive.com>,
linux-kernel@...r.kernel.org, Stephen Bates <sbates@...thlin.com>,
Zong Li <zong@...estech.com>, linux-mm@...ck.org,
Olof Johansson <olof@...om.net>,
linux-riscv@...ts.infradead.org,
Michael Clark <michaeljclark@....com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 5/5] RISC-V: Implement sparsemem
On 2018-10-11 10:24 a.m., Logan Gunthorpe wrote:
>
>
> On 2018-10-11 7:37 a.m., Christoph Hellwig wrote:
>>> +/*
>>> + * Log2 of the upper bound of the size of a struct page. Used for sizing
>>> + * the vmemmap region only, does not affect actual memory footprint.
>>> + * We don't use sizeof(struct page) directly since taking its size here
>>> + * requires its definition to be available at this point in the inclusion
>>> + * chain, and it may not be a power of 2 in the first place.
>>> + */
>>> +#define STRUCT_PAGE_MAX_SHIFT 6
>>
>> I know this is copied from arm64, but wouldn't this be a good time
>> to move this next to the struct page defintion?
Ok, I spoke too soon...
Having this define next to the struct page definition works great for
riscv. However, making that happen in arm64 seems to be a nightmare. The
include chain in arm64 is tangled up so much that including mm_types
where this is needed seems to be extremely difficult.
Unless you have any ideas, this might not be possible.
Logan
Powered by blists - more mailing lists