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
| ||
|
Date: Fri, 14 Jun 2013 13:37:05 +0800 From: Tang Chen <tangchen@...fujitsu.com> To: Michal Nazarewicz <mina86@...a86.com> CC: tglx@...utronix.de, mingo@...e.hu, hpa@...or.com, akpm@...ux-foundation.org, tj@...nel.org, trenn@...e.de, yinghai@...nel.org, jiang.liu@...wei.com, wency@...fujitsu.com, laijs@...fujitsu.com, isimatu.yasuaki@...fujitsu.com, mgorman@...e.de, minchan@...nel.org, gong.chen@...ux.intel.com, vasilis.liaskovitis@...fitbricks.com, lwoodman@...hat.com, riel@...hat.com, jweiner@...hat.com, prarit@...hat.com, x86@...nel.org, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: [Part3 PATCH v2 1/4] bootmem, mem-hotplug: Register local pagetable pages with LOCAL_NODE_DATA when freeing bootmem. Hi Michal, Please see below. On 06/13/2013 10:16 PM, Michal Nazarewicz wrote: ...... >> diff --git a/include/linux/memblock.h b/include/linux/memblock.h >> index a85ced9..8a38eef 100644 >> --- a/include/linux/memblock.h >> +++ b/include/linux/memblock.h >> @@ -131,6 +131,28 @@ void __next_free_mem_range_rev(u64 *idx, int nid, phys_addr_t *out_start, >> i != (u64)ULLONG_MAX; \ >> __next_free_mem_range_rev(&i, nid, p_start, p_end, p_nid)) >> >> +void __next_local_node_mem_range(int *idx, int nid, phys_addr_t *out_start, >> + phys_addr_t *out_end, int *out_nid); > > Why not make it return int? The same reason below. > >> + >> +/** >> + * for_each_local_node_mem_range - iterate memblock areas storing local node >> + * data >> + * @i: int used as loop variable >> + * @nid: node selector, %MAX_NUMNODES for all nodes >> + * @p_start: ptr to phys_addr_t for start address of the range, can be %NULL >> + * @p_end: ptr to phys_addr_t for end address of the range, can be %NULL >> + * @p_nid: ptr to int for nid of the range, can be %NULL >> + * >> + * Walks over memblock areas storing local node data. Since all the local node >> + * areas will be reserved by memblock, this iterator will only iterate >> + * memblock.reserve. Available as soon as memblock is initialized. >> + */ >> +#define for_each_local_node_mem_range(i, nid, p_start, p_end, p_nid) \ >> + for (i = -1, \ >> + __next_local_node_mem_range(&i, nid, p_start, p_end, p_nid); \ >> + i != -1; \ >> + __next_local_node_mem_range(&i, nid, p_start, p_end, p_nid)) >> + > > If __next_local_node_mem_range() returned int, this would be easier: > > +#define for_each_local_node_mem_range(i, nid, p_start, p_end, p_nid) \ > + for (i = -1; > + (i = __next_local_node_mem_range(i, nid, p_start, p_end, p_nid)) != -1; ) Yes, we can do it like this. But I tried to do something similar to for_each_free_mem_range and for_each_free_mem_range_reverse to keep the code coincident. How do you think to change all this similar functions into your way ? > ...... >> +void __init_memblock __next_local_node_mem_range(int *idx, int nid, >> + phys_addr_t *out_start, >> + phys_addr_t *out_end, int *out_nid) >> +{ >> + __next_flag_mem_range(idx, nid, MEMBLK_LOCAL_NODE, >> + out_start, out_end, out_nid); >> +} > > static inline in a header file perhaps? OK, will put it in a header file in the next version. Thanks. :) -- 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/
Powered by blists - more mailing lists