linux-kernel - [PATCH 3/3 (RFC)](memory hotplug) align maps for easy removing

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]

Date:	Fri, 14 Mar 2008 23:44:35 +0900
From:	Yasunori Goto <y-goto@...fujitsu.com>
To:	Badari Pulavarty <pbadari@...ibm.com>
Cc:	Linux Kernel ML <linux-kernel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Andrew Morton <akpm@...l.org>
Subject: [PATCH 3/3 (RFC)](memory hotplug) align maps for easy removing


To free memmap and usemap easier, this patch aligns these maps to page size.

I know usemap size is too small to align page size.
It will be waste of area. So, there may be better way than this.

Followings are pros. and cons with other my ideas.
But I'm not sure which is better way. 

a) Packing many section's usemap on one page. Count how many sections use
   it in page_count.
  Pros.
    - Avoid waisting area.
  Cons.
    - This usemap's page will be hard(or impossible) to remove due to
      dependency.
      It should be allocated on un-movable zone/node.
      (I'm not sure it's impact of performance.)
    - Nodes' structures may have to be packed like usemap???

b) Pack memmap and usemap in one allocation.
  Pros.
    - May avoid wasting area if its size is suitable.
  Cons.
    - If size is not suitable, it will be same as this patch.
    - This way is not good for VMEMMAP_SPARSEMEM.
      At least, it is reverse way against Yinghai-san's fix.

c) This way.
  Pros.
    - Very easy to remove.
  Cons.
    - Waist of area.

Any other idea is welcome.


Signed-off-by: Yasunori Goto <y-goto@...fujitsu.com>

---
 mm/sparse.c |    7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

Index: current/mm/sparse.c
===================================================================
--- current.orig/mm/sparse.c	2008-03-11 20:15:41.000000000 +0900
+++ current/mm/sparse.c	2008-03-11 20:58:18.000000000 +0900
@@ -244,7 +244,8 @@
 	struct mem_section *ms = __nr_to_section(pnum);
 	int nid = sparse_early_nid(ms);
 
-	usemap = alloc_bootmem_node(NODE_DATA(nid), usemap_size());
+	usemap = alloc_bootmem_pages_node(NODE_DATA(nid),
+					  PAGE_ALIGN(usemap_size()));
 	if (usemap)
 		return usemap;
 
@@ -264,8 +265,8 @@
 	if (map)
 		return map;
 
-	map = alloc_bootmem_node(NODE_DATA(nid),
-			sizeof(struct page) * PAGES_PER_SECTION);
+	map = alloc_bootmem_pages_node(NODE_DATA(nid),
+		       PAGE_ALIGN(sizeof(struct page) * PAGES_PER_SECTION));
 	return map;
 }
 #endif /* !CONFIG_SPARSEMEM_VMEMMAP */

-- 
Yasunori Goto 


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