linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Minchan Kim <minchan@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Tim Chen <tim.c.chen@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ying Huang <ying.huang@intel.com>
Subject: Re: [PATCH v2 3/5] mm: use a dedicated workqueue for the free workers
Date: Fri, 24 Mar 2017 20:37:10 +0800	[thread overview]
Message-ID: <20170324123710.GA10672@aaronlu.sh.intel.com> (raw)
In-Reply-To: <4549498a-befc-133d-b204-dd69b191e579@intel.com>

On Thu, Mar 23, 2017 at 08:38:43AM -0700, Dave Hansen wrote:
> On 03/22/2017 01:41 AM, Aaron Lu wrote:
> > On Wed, Mar 22, 2017 at 03:33:35PM +0900, Minchan Kim wrote:
> >> On Wed, Mar 15, 2017 at 05:00:02PM +0800, Aaron Lu wrote:
> >>> Introduce a workqueue for all the free workers so that user can fine
> >>> tune how many workers can be active through sysfs interface: max_active.
> >>> More workers will normally lead to better performance, but too many can
> >>> cause severe lock contention.
> >>
> >> Let me ask a question.
> >>
> >> How well can workqueue distribute the jobs in multiple CPU?
> > 
> > I would say it's good enough for my needs.
> > After all, it doesn't need many kworkers to achieve the 50% time
> > decrease: 2-4 kworkers for EP and 4-8 kworkers for EX are enough from
> > previous attched data.
> 
> It's also worth noting that we'd like to *also* like to look into
> increasing how scalable freeing pages to a given zone is.

Still on EX, I restricted the allocation to be only on node 1, with
120G memory allocated there:

max_active            time            compared to base  lock from perf
base(no parallel)     3.81s A+-3.3%     N/A               <1%
1                     3.10s A+-7.7%     a??18.6%            14.76%
2                     2.44s A+-13.6%    a??35.9%            36.95%
4                     2.07s A+-13.6%    a??45.6%            59.67%
8                     1.98s A+-0.4%     a??48.0%            62.59%
16                    2.01s A+-2.4%     a??47.2%            79.62%

If we can improve the scalibility of freeing a given zone, then parallel
free will be able to achieve more.

BTW, the lock is basically pgdat->lru_lock in release_pages and
zone->lock in free_pcppages_bulk:
    62.59%    62.59%  [kernel.kallsyms]  [k] native_queued_spin_lock_slowpath
37.17% native_queued_spin_lock_slowpath;_raw_spin_lock_irqsave;free_pcppages_bulk;free_hot_cold_page;free_hot_cold_page_list;release_pages;free_pages_and_swap_cache;tlb_flush_mmu_free_batches;batch_free_work;process_one_work;worker_thread;kthread;ret_from_fork
25.27% native_queued_spin_lock_slowpath;_raw_spin_lock_irqsave;release_pages;free_pages_and_swap_cache;tlb_flush_mmu_free_batches;batch_free_work;process_one_work;worker_thread;kthread;ret_from_fork

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-03-24 12:38 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15  8:59 [PATCH v2 0/5] mm: support parallel free of memory Aaron Lu
2017-03-15  9:00 ` [PATCH v2 1/5] mm: add tlb_flush_mmu_free_batches Aaron Lu
2017-03-15  9:00 ` [PATCH v2 2/5] mm: parallel free pages Aaron Lu
2017-03-15  9:42   ` Hillf Danton
2017-03-15 11:54     ` Aaron Lu
2017-03-15  9:00 ` [PATCH v2 3/5] mm: use a dedicated workqueue for the free workers Aaron Lu
2017-03-22  6:33   ` Minchan Kim
2017-03-22  8:41     ` Aaron Lu
2017-03-22  8:55       ` Minchan Kim
2017-03-22 13:43         ` Aaron Lu
2017-03-23  5:53           ` Minchan Kim
2017-03-23 15:38       ` Dave Hansen
2017-03-24 12:37         ` Aaron Lu [this message]
2017-03-15  9:00 ` [PATCH v2 4/5] mm: add force_free_pages in zap_pte_range Aaron Lu
2017-03-15  9:00 ` [PATCH v2 5/5] mm: add debugfs interface for parallel free tuning Aaron Lu
2017-03-15 14:18 ` [PATCH v2 0/5] mm: support parallel free of memory Michal Hocko
2017-03-15 15:44   ` Aaron Lu
2017-03-15 16:28     ` Michal Hocko
2017-03-15 21:38       ` Tim Chen
2017-03-16  9:07         ` Michal Hocko
2017-03-16 18:36           ` Tim Chen
2017-03-17  7:47             ` Michal Hocko
2017-03-17  8:07               ` Minchan Kim
2017-03-17 12:33               ` Aaron Lu
2017-03-17 12:59                 ` Michal Hocko
2017-03-17 13:16                 ` Peter Zijlstra
2017-03-17 12:53               ` Peter Zijlstra
2017-03-17 13:05                 ` Michal Hocko
2017-03-21 14:54           ` Dave Hansen
2017-03-22  8:02             ` Aaron Lu
2017-03-24  7:04             ` Aaron Lu
2017-03-21 15:18           ` Tim Chen
2017-03-16  6:54       ` Aaron Lu
2017-03-16  7:34       ` Aaron Lu
2017-03-16 13:51         ` Aaron Lu
2017-03-16 14:14           ` Aaron Lu
2017-03-15 14:56 ` Vlastimil Babka
2017-03-15 15:50   ` Aaron Lu
2017-03-17  3:10   ` Aaron Lu
2017-03-16 19:38 ` Alex Thorlton
2017-03-17  2:21   ` Aaron Lu
2017-03-20 19:15     ` Alex Thorlton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170324123710.GA10672@aaronlu.sh.intel.com \
    --to=aaron.lu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=tim.c.chen@intel.com \
    --cc=ying.huang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).