linux-kernel - Re: [RFC] [PATCH] virtual memmap on sparsemem v3 [2/4] generic virtual mem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061209221700.6feb2e5d.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Sat, 9 Dec 2006 22:17:00 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Heiko Carstens <heiko.carstens@...ibm.com>
Cc:	linux-kernel@...r.kernel.org, clameter@...r.sgi.com,
	apw@...dowen.org, akpm@...l.org
Subject: Re: [RFC] [PATCH] virtual memmap on sparsemem v3 [2/4] generic
 virtual mem_map on sparsemem

On Sat, 9 Dec 2006 13:05:47 +0100
Heiko Carstens <heiko.carstens@...ibm.com> wrote:

> > +#ifdef CONFIG_SPARSEMEM_VMEMMAP
> > +#if (((BITS_PER_LONG/4) * PAGES_PER_SECTION) % PAGE_SIZE) != 0
> > +#error "PAGE_SIZE/SECTION_SIZE relationship is not suitable for vmem_map"
> > +#endif
> 
> Why the BITS_PER_LONG/4? Or to put in other words: why not simply
> PAGES_PER_SECTION % PAGE_SIZE != 0 ?
> 
sorry, my mistake. What I wanted to do was

32bits arch --
4 * PAGES_PER_SECTION % PAGE_SIZE
64bits arch --
8 * PAGES_PER_SECTION % PAGE_SIZE

I'll renew this in the next week.

-Kame

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/