Message ID | 1503972142-289376-8-git-send-email-pasha.tatashin@oracle.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
From: Pavel Tatashin <pasha.tatashin@oracle.com> Date: Mon, 28 Aug 2017 22:02:18 -0400 > Add an optimized mm_zero_struct_page(), so struct page's are zeroed without > calling memset(). We do eight to ten regular stores based on the size of > struct page. Compiler optimizes out the conditions of switch() statement. > > SPARC-M6 with 15T of memory, single thread performance: > > BASE FIX OPTIMIZED_FIX > bootmem_init 28.440467985s 2.305674818s 2.305161615s > free_area_init_nodes 202.845901673s 225.343084508s 172.556506560s > -------------------------------------------- > Total 231.286369658s 227.648759326s 174.861668175s > > BASE: current linux > FIX: This patch series without "optimized struct page zeroing" > OPTIMIZED_FIX: This patch series including the current patch. > > bootmem_init() is where memory for struct pages is zeroed during > allocation. Note, about two seconds in this function is a fixed time: it > does not increase as memory is increased. > > Signed-off-by: Pavel Tatashin <pasha.tatashin@oracle.com> > Reviewed-by: Steven Sistare <steven.sistare@oracle.com> > Reviewed-by: Daniel Jordan <daniel.m.jordan@oracle.com> > Reviewed-by: Bob Picco <bob.picco@oracle.com> You should probably use initializing stores when you are doing 8 stores and we thus know the page struct is cache line aligned. But other than that: Acked-by: David S. Miller <davem@davemloft.net>
Hi Dave, Thank you for acking. The reason I am not doing initializing stores is because they require a membar, even if only regular stores are following (I hoped to do a membar before first load). This is something I was thinking was not true, but after consulting with colleagues and checking processor manual, I verified that it is the case. Pasha > > You should probably use initializing stores when you are doing 8 > stores and we thus know the page struct is cache line aligned. > > But other than that: > > Acked-by: David S. Miller <davem@davemloft.net>
From: Pasha Tatashin <pasha.tatashin@oracle.com> Date: Wed, 30 Aug 2017 09:19:58 -0400 > The reason I am not doing initializing stores is because they require > a membar, even if only regular stores are following (I hoped to do a > membar before first load). This is something I was thinking was not > true, but after consulting with colleagues and checking processor > manual, I verified that it is the case. Oh yes, that's right, now I remember.
diff --git a/arch/sparc/include/asm/pgtable_64.h b/arch/sparc/include/asm/pgtable_64.h index 6fbd931f0570..cee5cc7ccc51 100644 --- a/arch/sparc/include/asm/pgtable_64.h +++ b/arch/sparc/include/asm/pgtable_64.h @@ -230,6 +230,36 @@ extern unsigned long _PAGE_ALL_SZ_BITS; extern struct page *mem_map_zero; #define ZERO_PAGE(vaddr) (mem_map_zero) +/* This macro must be updated when the size of struct page grows above 80 + * or reduces below 64. + * The idea that compiler optimizes out switch() statement, and only + * leaves clrx instructions + */ +#define mm_zero_struct_page(pp) do { \ + unsigned long *_pp = (void *)(pp); \ + \ + /* Check that struct page is either 64, 72, or 80 bytes */ \ + BUILD_BUG_ON(sizeof(struct page) & 7); \ + BUILD_BUG_ON(sizeof(struct page) < 64); \ + BUILD_BUG_ON(sizeof(struct page) > 80); \ + \ + switch (sizeof(struct page)) { \ + case 80: \ + _pp[9] = 0; /* fallthrough */ \ + case 72: \ + _pp[8] = 0; /* fallthrough */ \ + default: \ + _pp[7] = 0; \ + _pp[6] = 0; \ + _pp[5] = 0; \ + _pp[4] = 0; \ + _pp[3] = 0; \ + _pp[2] = 0; \ + _pp[1] = 0; \ + _pp[0] = 0; \ + } \ +} while (0) + /* PFNs are real physical page numbers. However, mem_map only begins to record * per-page information starting at pfn_base. This is to handle systems where * the first physical page in the machine is at some huge physical address,