Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1626902
| From | "Huang\, Ying" <ying.huang@intel.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH -mm -v9 2/3] mm, THP, swap: Check whether THP can be split firstly |
| Date | 2017-04-20 03:00 +0200 |
| Message-ID | <ty8BY-1Xk-5@gated-at.bofh.it> (permalink) |
| References | <txRUu-lm-9@gated-at.bofh.it> <txRUu-lm-7@gated-at.bofh.it> <ty0uK-5Cb-29@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Johannes Weiner <hannes@cmpxchg.org> writes: > On Wed, Apr 19, 2017 at 03:06:24PM +0800, Huang, Ying wrote: >> From: Huang Ying <ying.huang@intel.com> >> >> To swap out THP (Transparent Huage Page), before splitting the THP, >> the swap cluster will be allocated and the THP will be added into the >> swap cache. But it is possible that the THP cannot be split, so that >> we must delete the THP from the swap cache and free the swap cluster. >> To avoid that, in this patch, whether the THP can be split is checked >> firstly. The check can only be done racy, but it is good enough for >> most cases. >> >> With the patchset, the swap out throughput improves 3.6% (from about >> 4.16GB/s to about 4.31GB/s) in the vm-scalability swap-w-seq test case >> with 8 processes. The test is done on a Xeon E5 v3 system. The swap >> device used is a RAM simulated PMEM (persistent memory) device. To >> test the sequential swapping out, the test case creates 8 processes, >> which sequentially allocate and write to the anonymous pages until the >> RAM and part of the swap device is used up. >> >> Cc: Johannes Weiner <hannes@cmpxchg.org> >> Signed-off-by: "Huang, Ying" <ying.huang@intel.com> >> Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> [for can_split_huge_page()] > > How often does this actually happen in practice? Because all that this > protects us from is trying to allocate a swap cluster - which with the > si->free_clusters list really isn't all that expensive - and return it > again. Unless this happens all the time in practice, this optimization > seems misplaced. In addition to allocate/free swap cluster, add/delete to/from the swap cache will be called too. > It's especially a little strange because in the other email I asked > about the need for unlikely() annotations, yet this patch is adding > branches and checks for what seems to be an unlikely condition into > the THP hot path. > > I'd suggest you drop both these optimization attempts unless there is > real data proving that they have a measurable impact. To my surprise too, I found this patch has measurable impact in my test. The swap out throughput improves 3.6% in the vm-scalability swap-w-seq test case with 8 processes. Details are in the original patch description. Best Regards, Huang, Ying
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH -mm -v9 2/3] mm, THP, swap: Check whether THP can be split firstly "Huang, Ying" <ying.huang@intel.com> - 2017-04-19 09:10 +0200
Re: [PATCH -mm -v9 2/3] mm, THP, swap: Check whether THP can be split firstly Johannes Weiner <hannes@cmpxchg.org> - 2017-04-19 18:20 +0200
Re: [PATCH -mm -v9 2/3] mm, THP, swap: Check whether THP can be split firstly "Huang\, Ying" <ying.huang@intel.com> - 2017-04-20 03:00 +0200
Re: [PATCH -mm -v9 2/3] mm, THP, swap: Check whether THP can be split firstly Johannes Weiner <hannes@cmpxchg.org> - 2017-04-20 23:00 +0200
Re: [PATCH -mm -v9 2/3] mm, THP, swap: Check whether THP can be split firstly "Huang\, Ying" <ying.huang@intel.com> - 2017-04-21 02:40 +0200
csiph-web