linux-kernel - Re: [RFC][PATCH] page->mapping clarification [1/3] base functions

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] [day] [month] [year] [list]

Message-Id: <20070927065046.508d33c0.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Thu, 27 Sep 2007 06:50:46 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Hugh Dickins <hugh@...itas.com>
Cc:	clameter@....com, linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	akpm@...ux-foundation.org, nickpiggin@...oo.com.au,
	ricknu-0@...dent.ltu.se, magnus.damm@...il.com
Subject: Re: [RFC][PATCH] page->mapping clarification [1/3] base functions

On Wed, 26 Sep 2007 20:31:02 +0100 (BST)
Hugh Dickins <hugh@...itas.com> wrote:
> Would that waste a little memory?  I think not with SLUB,
> but perhaps with SLOB, which packs a little tighter.
> 

maybe just depends on the amount of used anon_vma and page_mapping_info etc...
I don't think a system which uses SLOB consumes such structs so much
as that memory-for-alignment is considered as "waste" of memory.

Anyway, I decided to go ahead with current container-info-per-page
implementation. If the size of page struct is problem at mainline inclusion
discussion, I'll be back.

Thanks,
-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/